Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e6e808a3d88096cf7e0def4e81a4cd2cf7cd3eddb742288f410370d5895cf95

Tx prefix hash: d82fe74e3f3c630d57f45b487fc42059e0ecd1c503a842bdb66ee351364e968e
Tx public key: 96a4e5e511ab54a879d68cb4e83aa34b3c4e71c690c75c2db58db56027562d9a
Timestamp: 1711142312 Timestamp [UCT]: 2024-03-22 21:18:32 Age [y:d:h:m:s]: 00:236:11:12:55
Block: 984143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169265 RingCT/type: yes/0
Extra: 0196a4e5e511ab54a879d68cb4e83aa34b3c4e71c690c75c2db58db56027562d9a02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 048e587149f19b08f32c6fb43971d858c782a20b59975d940397227b755edba4 0.600000000000 1444302 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": 984153, "vin": [ { "gen": { "height": 984143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "048e587149f19b08f32c6fb43971d858c782a20b59975d940397227b755edba4" } } ], "extra": [ 1, 150, 164, 229, 229, 17, 171, 84, 168, 121, 214, 140, 180, 232, 58, 163, 75, 60, 78, 113, 198, 144, 199, 92, 45, 181, 141, 181, 96, 39, 86, 45, 154, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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