Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d337d3cc3628f937d8e624f8cf0392973bd08184f4f2d60b3bd50c9935d9d9c9

Tx prefix hash: 5448013ebbe92eaf53cf65aa65a03d7017b039c294c8c47ec144fdc473b87f9e
Tx public key: ad12273c912c2e606e11f9903877aeb3c61a0b2de287194c1140689bbe924a9d
Timestamp: 1720386240 Timestamp [UCT]: 2024-07-07 21:04:00 Age [y:d:h:m:s]: 00:271:08:28:57
Block: 1060753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193878 RingCT/type: yes/0
Extra: 01ad12273c912c2e606e11f9903877aeb3c61a0b2de287194c1140689bbe924a9d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f560d6c931fd3224d9e1024ee292cce1f5c2a13155d40a25f538b611758ef3cc 0.600000000000 1531238 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": 1060763, "vin": [ { "gen": { "height": 1060753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f560d6c931fd3224d9e1024ee292cce1f5c2a13155d40a25f538b611758ef3cc" } } ], "extra": [ 1, 173, 18, 39, 60, 145, 44, 46, 96, 110, 17, 249, 144, 56, 119, 174, 179, 198, 26, 11, 45, 226, 135, 25, 76, 17, 64, 104, 155, 190, 146, 74, 157, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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