Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 913b76da0ae491ebfc2b9079ea22a88b73ad1f21560d4e40fa4dd0e8715ceec2

Tx prefix hash: cf5921c436b100a62d2c0c54000e11519f2c8fd6ad1524a00efe28f68104ff85
Tx public key: b110a236e36ec041f6aee9c3a53351e51120d1db965e2261a8af7cd58b7358ac
Timestamp: 1718682009 Timestamp [UCT]: 2024-06-18 03:40:09 Age [y:d:h:m:s]: 00:358:17:07:30
Block: 1046629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256369 RingCT/type: yes/0
Extra: 01b110a236e36ec041f6aee9c3a53351e51120d1db965e2261a8af7cd58b7358ac0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b36f9d195634c77cc3c62e4615fe29e540cfc8076d63ea5460ce661e6d3fff56 0.600000000000 1516446 of 15

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": 1046639, "vin": [ { "gen": { "height": 1046629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b36f9d195634c77cc3c62e4615fe29e540cfc8076d63ea5460ce661e6d3fff56" } } ], "extra": [ 1, 177, 16, 162, 54, 227, 110, 192, 65, 246, 174, 233, 195, 165, 51, 81, 229, 17, 32, 209, 219, 150, 94, 34, 97, 168, 175, 124, 213, 139, 115, 88, 172, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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