Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6debe1f7d4a753b2ae99decf1d5e5a4917c740a7abf369c71a5a68114901fdb

Tx prefix hash: a5e4590ce1f64bd670228dc5de50641cb7ec0f0d38bd33abf4595c6b2e6fcb1d
Tx public key: 29add237b7aa1821cfc7120d2817575fadff92d73d303620e7f1274398764eee
Timestamp: 1729756449 Timestamp [UCT]: 2024-10-24 07:54:09 Age [y:d:h:m:s]: 00:092:17:09:39
Block: 1138413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66252 RingCT/type: yes/0
Extra: 0129add237b7aa1821cfc7120d2817575fadff92d73d303620e7f1274398764eee021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 108c5f269cde0eb79f3e422857f5ed698b14156c7cc939dee95eda2e9f035905 0.600000000000 1622076 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": 1138423, "vin": [ { "gen": { "height": 1138413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "108c5f269cde0eb79f3e422857f5ed698b14156c7cc939dee95eda2e9f035905" } } ], "extra": [ 1, 41, 173, 210, 55, 183, 170, 24, 33, 207, 199, 18, 13, 40, 23, 87, 95, 173, 255, 146, 215, 61, 48, 54, 32, 231, 241, 39, 67, 152, 118, 78, 238, 2, 17, 0, 0, 0, 3, 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