Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3b58022dce9414e1e2c13b4916f9e4e1ced525a53ce93066c336f8723a061b

Tx prefix hash: 3c9f6954950f245f80c8bd5cff1045c2d0067eb1e50eca2db71b0ecd129bbdb9
Tx public key: c31dbdc5edfed1f9ddfd343abee3c2642a8692528b51005df88805b48206e0b8
Timestamp: 1730306366 Timestamp [UCT]: 2024-10-30 16:39:26 Age [y:d:h:m:s]: 00:140:23:27:32
Block: 1142929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100597 RingCT/type: yes/0
Extra: 01c31dbdc5edfed1f9ddfd343abee3c2642a8692528b51005df88805b48206e0b802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b91e6d64fa44e5e5050431e3b3813899d64fcd68fa0a54b3a009ab7399683aeb 0.600000000000 1626786 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": 1142939, "vin": [ { "gen": { "height": 1142929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b91e6d64fa44e5e5050431e3b3813899d64fcd68fa0a54b3a009ab7399683aeb" } } ], "extra": [ 1, 195, 29, 189, 197, 237, 254, 209, 249, 221, 253, 52, 58, 190, 227, 194, 100, 42, 134, 146, 82, 139, 81, 0, 93, 248, 136, 5, 180, 130, 6, 224, 184, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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