Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10780cf5e83cfaab37b9b847826fdf7182f8c8e9a5b285aa077f1711fb279a66

Tx prefix hash: 118aa10f0def010979a769ec2e12a921fa5a9ac199762d5c56c7db5970fe4638
Tx public key: c73ddc9cdb5b8a8fd21120a17e0d2600b9d6f82cff898fc538dd6a04e6591bbb
Timestamp: 1728081058 Timestamp [UCT]: 2024-10-04 22:30:58 Age [y:d:h:m:s]: 00:232:12:40:54
Block: 1124548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166027 RingCT/type: yes/0
Extra: 01c73ddc9cdb5b8a8fd21120a17e0d2600b9d6f82cff898fc538dd6a04e6591bbb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd65277213d85c6fa422d21692613f2e0601052762944a8a525b17595f507ea7 0.600000000000 1607187 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": 1124558, "vin": [ { "gen": { "height": 1124548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd65277213d85c6fa422d21692613f2e0601052762944a8a525b17595f507ea7" } } ], "extra": [ 1, 199, 61, 220, 156, 219, 91, 138, 143, 210, 17, 32, 161, 126, 13, 38, 0, 185, 214, 248, 44, 255, 137, 143, 197, 56, 221, 106, 4, 230, 89, 27, 187, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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