Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc8f66ed3ef8b58c1452467148f08574b2713d8c6b0c7b84c3ba9dac68c57236

Tx prefix hash: 2e468f0a3e1a9a44b4f627ea83fb7f7ec06a45a8dd8a27fab08651f913ac0ab4
Tx public key: e2dae023b7f2119ca044ea050ca6456d9650732c4f1366e6d3148c79601ede9b
Timestamp: 1726953012 Timestamp [UCT]: 2024-09-21 21:10:12 Age [y:d:h:m:s]: 00:174:03:35:15
Block: 1115198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124289 RingCT/type: yes/0
Extra: 01e2dae023b7f2119ca044ea050ca6456d9650732c4f1366e6d3148c79601ede9b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fff17bc1a056768c3bd93f360638e86802d0eadfc35508abea631d4045dbce3 0.600000000000 1595249 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": 1115208, "vin": [ { "gen": { "height": 1115198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fff17bc1a056768c3bd93f360638e86802d0eadfc35508abea631d4045dbce3" } } ], "extra": [ 1, 226, 218, 224, 35, 183, 242, 17, 156, 160, 68, 234, 5, 12, 166, 69, 109, 150, 80, 115, 44, 79, 19, 102, 230, 211, 20, 140, 121, 96, 30, 222, 155, 2, 17, 0, 0, 0, 3, 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