Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcb013ebcafa191cad3b60bacec23876296b29918b770bcfa053aa0a7c78802f

Tx prefix hash: 00ded1f585746d83a05512b8d9ed9aa6d66c70607089008be6796ee7a3a5bfb3
Tx public key: dd1a299cd9289281db238fa0aec44e548cebf92d4b158b68d0cba0b922c4db2a
Timestamp: 1727943519 Timestamp [UCT]: 2024-10-03 08:18:39 Age [y:d:h:m:s]: 00:255:10:25:15
Block: 1123410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182303 RingCT/type: yes/0
Extra: 01dd1a299cd9289281db238fa0aec44e548cebf92d4b158b68d0cba0b922c4db2a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5172cde704ac7345b05362be415ea72b522f7b83762baf077bb3154bafc750c9 0.600000000000 1605943 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": 1123420, "vin": [ { "gen": { "height": 1123410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5172cde704ac7345b05362be415ea72b522f7b83762baf077bb3154bafc750c9" } } ], "extra": [ 1, 221, 26, 41, 156, 217, 40, 146, 129, 219, 35, 143, 160, 174, 196, 78, 84, 140, 235, 249, 45, 75, 21, 139, 104, 208, 203, 160, 185, 34, 196, 219, 42, 2, 17, 0, 0, 0, 3, 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