Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 799a4550c529d3c63bfcbd9b1dd7f3d0ffaec49649d1f3503a17789de7ffbcda

Tx prefix hash: 351c63f7771da4cf4eab3e25e76d2a7370d0f78c40d969962455cedb98f3e137
Tx public key: cabd0ab9c5a323fc7e737550209d8a43923f99aef5304b7964cccb475d3db81e
Timestamp: 1742764661 Timestamp [UCT]: 2025-03-23 21:17:41 Age [y:d:h:m:s]: 00:243:02:05:16
Block: 1245792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171481 RingCT/type: yes/0
Extra: 01cabd0ab9c5a323fc7e737550209d8a43923f99aef5304b7964cccb475d3db81e021100000006c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a9cb7bc76896e97a858e2663eaec23f1b4acfbdb980500a17a94528e204ad5 0.600000000000 1732783 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": 1245802, "vin": [ { "gen": { "height": 1245792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a9cb7bc76896e97a858e2663eaec23f1b4acfbdb980500a17a94528e204ad5" } } ], "extra": [ 1, 202, 189, 10, 185, 197, 163, 35, 252, 126, 115, 117, 80, 32, 157, 138, 67, 146, 63, 153, 174, 245, 48, 75, 121, 100, 204, 203, 71, 93, 61, 184, 30, 2, 17, 0, 0, 0, 6, 198, 116, 9, 88, 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