Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61fa20503e10b958498ca119d95805dc395965b036e8c376fb648e23c5147bf3

Tx prefix hash: e611bba15045b8b3102ce4aca2d4a1dd8ce6df5f14791c31f68c943a54ae68f8
Tx public key: 054287587aacfa8002b531cec88a82103edaa80d0c9e13e4684b065b1bffb2ee
Timestamp: 1710737235 Timestamp [UCT]: 2024-03-18 04:47:15 Age [y:d:h:m:s]: 01:008:01:51:37
Block: 980786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266715 RingCT/type: yes/0
Extra: 01054287587aacfa8002b531cec88a82103edaa80d0c9e13e4684b065b1bffb2ee02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e341c3f3aeffc21c82af0fb36f76216023dd4e6dfe9e0739d08e90b5e9b0d52b 0.600000000000 1440867 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": 980796, "vin": [ { "gen": { "height": 980786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e341c3f3aeffc21c82af0fb36f76216023dd4e6dfe9e0739d08e90b5e9b0d52b" } } ], "extra": [ 1, 5, 66, 135, 88, 122, 172, 250, 128, 2, 181, 49, 206, 200, 138, 130, 16, 62, 218, 168, 13, 12, 158, 19, 228, 104, 75, 6, 91, 27, 255, 178, 238, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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