Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7927b01a8b86d5f7ab711aa4e27586034ff3a7e45feaa0ab943efad79d6de8d9

Tx prefix hash: 36dc2e6398670d7a422965abecc9c375588ba2a4b60c6d5e75b5e604e933abe1
Tx public key: d1a0cc2093b2c21a6ee7a1935105871897fad70e1d540d36e457f0ccfa76214a
Timestamp: 1575819330 Timestamp [UCT]: 2019-12-08 15:35:30 Age [y:d:h:m:s]: 05:133:11:40:10
Block: 23304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1241269 RingCT/type: yes/0
Extra: 01d1a0cc2093b2c21a6ee7a1935105871897fad70e1d540d36e457f0ccfa76214a02110000003b9159db1e000000000000000000

1 output(s) for total of 513.789288866000 dcy

stealth address amount amount idx
00: 449b9af87d408fa9ebf3e55cf54f8389c8c9ca166e1086eff5dfad6520c9c9e1 513.789288866000 37249 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 23314, "vin": [ { "gen": { "height": 23304 } } ], "vout": [ { "amount": 513789288866, "target": { "key": "449b9af87d408fa9ebf3e55cf54f8389c8c9ca166e1086eff5dfad6520c9c9e1" } } ], "extra": [ 1, 209, 160, 204, 32, 147, 178, 194, 26, 110, 231, 161, 147, 81, 5, 135, 24, 151, 250, 215, 14, 29, 84, 13, 54, 228, 87, 240, 204, 250, 118, 33, 74, 2, 17, 0, 0, 0, 59, 145, 89, 219, 30, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8