Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3f3f1818980ad64143368927cdc241268b198520d00ca1f65fcb439fd4af237

Tx prefix hash: e061b86f11258183ab95c1ea0b0fe4a586d50139b1945b49145357cf5331d32f
Tx public key: 4ed3f57ae426da4f69d54f4659ea9dfe7ce91fd21d18b21d1d3444bd12c39afa
Timestamp: 1699804102 Timestamp [UCT]: 2023-11-12 15:48:22 Age [y:d:h:m:s]: 01:134:07:58:53
Block: 890128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357160 RingCT/type: yes/0
Extra: 014ed3f57ae426da4f69d54f4659ea9dfe7ce91fd21d18b21d1d3444bd12c39afa02110000000649378ead000000000000000000

1 output(s) for total of 0.689662201000 dcy

stealth address amount amount idx
00: 00c2c1d1ea019f80b853f1a5d328aac0dda851d3552caa9f54145acff3aef82d 0.689662201000 1346147 of 0

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": 890138, "vin": [ { "gen": { "height": 890128 } } ], "vout": [ { "amount": 689662201, "target": { "key": "00c2c1d1ea019f80b853f1a5d328aac0dda851d3552caa9f54145acff3aef82d" } } ], "extra": [ 1, 78, 211, 245, 122, 228, 38, 218, 79, 105, 213, 79, 70, 89, 234, 157, 254, 124, 233, 31, 210, 29, 24, 178, 29, 29, 52, 68, 189, 18, 195, 154, 250, 2, 17, 0, 0, 0, 6, 73, 55, 142, 173, 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