Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7257acb44639919d7baed5c3fe92eb2bacb3c171ea3b3875ba4f7f9a4860da08

Tx prefix hash: 9445cbb1a2d4eb5e427624a6907fd6fcb748b63143898e0085d07861a6579712
Tx public key: 054786d866dba8ed5ef127f4e68df2a64db026f2b7235007d25cae32a7a23d4f
Timestamp: 1729840014 Timestamp [UCT]: 2024-10-25 07:06:54 Age [y:d:h:m:s]: 00:030:00:44:25
Block: 1139098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21451 RingCT/type: yes/0
Extra: 01054786d866dba8ed5ef127f4e68df2a64db026f2b7235007d25cae32a7a23d4f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d52001a2cdd4f78934d0a80897ee902117ac894a498d1a80c7d322ea814c3349 0.600000000000 1622859 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": 1139108, "vin": [ { "gen": { "height": 1139098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d52001a2cdd4f78934d0a80897ee902117ac894a498d1a80c7d322ea814c3349" } } ], "extra": [ 1, 5, 71, 134, 216, 102, 219, 168, 237, 94, 241, 39, 244, 230, 141, 242, 166, 77, 176, 38, 242, 183, 35, 80, 7, 210, 92, 174, 50, 167, 162, 61, 79, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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