Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17db72d7044fbce5485bf03d2c78114202979a0dffd01a50df56f132152ea409

Tx prefix hash: 7440240ad8ae367f293ff613c458988a8863a5b0d1cb8062a68441531ab2b8e8
Tx public key: ed4bb50bb4519d8c58e98ca3c4bfce88b4a7423bbfb16b11f4340164b5b9b40f
Timestamp: 1713377152 Timestamp [UCT]: 2024-04-17 18:05:52 Age [y:d:h:m:s]: 00:266:12:07:56
Block: 1002645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190764 RingCT/type: yes/0
Extra: 01ed4bb50bb4519d8c58e98ca3c4bfce88b4a7423bbfb16b11f4340164b5b9b40f02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdb48f4cc848ead9b98e26dbefdcb7f8ed5fcd90ff534921a16d61df7134db94 0.600000000000 1463163 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": 1002655, "vin": [ { "gen": { "height": 1002645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdb48f4cc848ead9b98e26dbefdcb7f8ed5fcd90ff534921a16d61df7134db94" } } ], "extra": [ 1, 237, 75, 181, 11, 180, 81, 157, 140, 88, 233, 140, 163, 196, 191, 206, 136, 180, 167, 66, 59, 191, 177, 107, 17, 244, 52, 1, 100, 181, 185, 180, 15, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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