Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2619aef812f6fb1c389a870042fd8de6de8f62ebc70e974dda8b48fbd08589e

Tx prefix hash: 581f8b78ccc08276838de66fa275a06b092a5b926bf142ca96b6b6365817b187
Tx public key: 8d2fb6893f0a0836408062e2e5e92c42a65e51cb43bb329bfbd32120ed48e4d0
Timestamp: 1731940489 Timestamp [UCT]: 2024-11-18 14:34:49 Age [y:d:h:m:s]: 00:364:19:12:41
Block: 1156448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258276 RingCT/type: yes/0
Extra: 018d2fb6893f0a0836408062e2e5e92c42a65e51cb43bb329bfbd32120ed48e4d0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d49e1ba223212e0eaa20da3d388ca12cc9a03ab7c5062123da675fcc2ee410d3 0.600000000000 1642071 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": 1156458, "vin": [ { "gen": { "height": 1156448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d49e1ba223212e0eaa20da3d388ca12cc9a03ab7c5062123da675fcc2ee410d3" } } ], "extra": [ 1, 141, 47, 182, 137, 63, 10, 8, 54, 64, 128, 98, 226, 229, 233, 44, 66, 166, 94, 81, 203, 67, 187, 50, 155, 251, 211, 33, 32, 237, 72, 228, 208, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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