Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3542fb9f795c8ca2fcb12004da9102518d43a302b1f293ec219afb0b715822eb

Tx prefix hash: 11e72d97a5e9b24d0debd4b902a46b91c249721a42bba81b707ac2ced12e1d5d
Tx public key: f89ec748d773567319a8c09180a75c5ef6bcc80781a3930ccd01392def3d1f64
Timestamp: 1727181628 Timestamp [UCT]: 2024-09-24 12:40:28 Age [y:d:h:m:s]: 00:202:03:56:42
Block: 1117092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144311 RingCT/type: yes/0
Extra: 01f89ec748d773567319a8c09180a75c5ef6bcc80781a3930ccd01392def3d1f6402110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef7f05eda27b392bc63e7b2b5a4868b37f336039070dab33f1ce969c8d7968aa 0.600000000000 1597803 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": 1117102, "vin": [ { "gen": { "height": 1117092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef7f05eda27b392bc63e7b2b5a4868b37f336039070dab33f1ce969c8d7968aa" } } ], "extra": [ 1, 248, 158, 199, 72, 215, 115, 86, 115, 25, 168, 192, 145, 128, 167, 92, 94, 246, 188, 200, 7, 129, 163, 147, 12, 205, 1, 57, 45, 239, 61, 31, 100, 2, 17, 0, 0, 0, 10, 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