Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73fc56c3fc5d5d2944955f74f8080c6d3b9039f462095cc47962a862fd207b84

Tx prefix hash: 8dd02335d9dbf4eb6d0aa563328fc1e4c3719756818eb5b8b619b6075f83ffe3
Tx public key: f67a962c530dc3716c7dca48845d75f92372173e8604f80a63f750f6d1882b90
Timestamp: 1737723371 Timestamp [UCT]: 2025-01-24 12:56:11 Age [y:d:h:m:s]: 00:049:03:04:42
Block: 1204297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34933 RingCT/type: yes/0
Extra: 01f67a962c530dc3716c7dca48845d75f92372173e8604f80a63f750f6d1882b900211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c609cf05f6e8f8d1daf0a203e8aaa928b0ceada40153f0d6b6140008e1025af 0.600000000000 1690982 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": 1204307, "vin": [ { "gen": { "height": 1204297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c609cf05f6e8f8d1daf0a203e8aaa928b0ceada40153f0d6b6140008e1025af" } } ], "extra": [ 1, 246, 122, 150, 44, 83, 13, 195, 113, 108, 125, 202, 72, 132, 93, 117, 249, 35, 114, 23, 62, 134, 4, 248, 10, 99, 247, 80, 246, 209, 136, 43, 144, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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