Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82094ddc5f4166ead7bb8b8dc910bd5688509791d02015684746b293d9a334c8

Tx prefix hash: 5808843d527e2f95305840d77a2d1facdffc33167a5166f2fcd62cfe80aa4e29
Tx public key: 0e5ba9f66924c934be7f1842cd6027dda3b3985e16d0731321c1a83b29cd6c18
Timestamp: 1717452495 Timestamp [UCT]: 2024-06-03 22:08:15 Age [y:d:h:m:s]: 00:300:14:55:02
Block: 1036438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214843 RingCT/type: yes/0
Extra: 010e5ba9f66924c934be7f1842cd6027dda3b3985e16d0731321c1a83b29cd6c180211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd340e5b45a0db4eaf37392f546bd23587fd59694104b0c8db241271debf94c2 0.600000000000 1504965 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": 1036448, "vin": [ { "gen": { "height": 1036438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd340e5b45a0db4eaf37392f546bd23587fd59694104b0c8db241271debf94c2" } } ], "extra": [ 1, 14, 91, 169, 246, 105, 36, 201, 52, 190, 127, 24, 66, 205, 96, 39, 221, 163, 179, 152, 94, 22, 208, 115, 19, 33, 193, 168, 59, 41, 205, 108, 24, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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