Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d83749705e5e8ec27400a68d3b343822c08b507a6c35a69f4e4e7db014f87817

Tx prefix hash: bc0d2376de48164e6564f3ee1efc982b1591cacb7e2c684dad325ee4ab8c0d97
Tx public key: f511a5b000717dd54937aae8c9d486fb1aa53a1a4394c54bf609a1f4a4f9c015
Timestamp: 1727747159 Timestamp [UCT]: 2024-10-01 01:45:59 Age [y:d:h:m:s]: 00:100:12:36:34
Block: 1121784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71869 RingCT/type: yes/0
Extra: 01f511a5b000717dd54937aae8c9d486fb1aa53a1a4394c54bf609a1f4a4f9c01502110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 793d75d67cd3202eb11b4b565aa5880fe72d41ed132b3d12c71f0f54c89dc994 0.600000000000 1604129 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": 1121794, "vin": [ { "gen": { "height": 1121784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "793d75d67cd3202eb11b4b565aa5880fe72d41ed132b3d12c71f0f54c89dc994" } } ], "extra": [ 1, 245, 17, 165, 176, 0, 113, 125, 213, 73, 55, 170, 232, 201, 212, 134, 251, 26, 165, 58, 26, 67, 148, 197, 75, 246, 9, 161, 244, 164, 249, 192, 21, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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