Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb74d0d1f838ae3bba043cacb351c473c2d8ade454b9edabc517a687b9579820

Tx prefix hash: 8030bf6dd034fb2449e9d3cf0490ed9b8bb6479df2b854c2c6c3c118cd3737ca
Tx public key: ff41b9087824ab4b9547b815d290ce927b7fbae82a08efd33e50050e7eb9008b
Timestamp: 1720334584 Timestamp [UCT]: 2024-07-07 06:43:04 Age [y:d:h:m:s]: 00:277:16:14:03
Block: 1060325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198397 RingCT/type: yes/0
Extra: 01ff41b9087824ab4b9547b815d290ce927b7fbae82a08efd33e50050e7eb9008b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c455b6f533b0d411a8f5f753aafd6056ff0ef4943199c11e77533e1d4c39bfc 0.600000000000 1530802 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": 1060335, "vin": [ { "gen": { "height": 1060325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c455b6f533b0d411a8f5f753aafd6056ff0ef4943199c11e77533e1d4c39bfc" } } ], "extra": [ 1, 255, 65, 185, 8, 120, 36, 171, 75, 149, 71, 184, 21, 210, 144, 206, 146, 123, 127, 186, 232, 42, 8, 239, 211, 62, 80, 5, 14, 126, 185, 0, 139, 2, 17, 0, 0, 0, 1, 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