Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45d6bf37832374df06ca21ea9fbe66e30672ecccf65a9196a3ddfdcde51db7b8

Tx prefix hash: cdf449791d07e13ffeae7ab1ef4105c6e1b02a6ec8ee8297ac91ef5d575b1fad
Tx public key: 9735d73c842859e74e211201a2f1b9fc681b0bf368f3bcfd8c42a7f4da84dff0
Timestamp: 1736185084 Timestamp [UCT]: 2025-01-06 17:38:04 Age [y:d:h:m:s]: 00:350:15:10:15
Block: 1191610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248148 RingCT/type: yes/0
Extra: 019735d73c842859e74e211201a2f1b9fc681b0bf368f3bcfd8c42a7f4da84dff0021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a6c00b059a29f6be1b6de7e8608f56db9e0cf47776568933d52b0ec3d87967b 0.600000000000 1678149 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": 1191620, "vin": [ { "gen": { "height": 1191610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a6c00b059a29f6be1b6de7e8608f56db9e0cf47776568933d52b0ec3d87967b" } } ], "extra": [ 1, 151, 53, 215, 60, 132, 40, 89, 231, 78, 33, 18, 1, 162, 241, 185, 252, 104, 27, 11, 243, 104, 243, 188, 253, 140, 66, 167, 244, 218, 132, 223, 240, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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