Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5825592ca19f35516b79cfa79e97a3b872b4ae663e0920cb146ad40f929cfdd

Tx prefix hash: 397e2e37230353c6eb8c99b8c7605285c61dedc0a80a7aa97d0fd38e4ce1dad3
Tx public key: 0db16352f1b8f43b4d86f9ed70bdf62839d812e959f4eba44ada7cfc60e56d1b
Timestamp: 1594515642 Timestamp [UCT]: 2020-07-12 01:00:42 Age [y:d:h:m:s]: 04:132:09:33:46
Block: 116918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1040833 RingCT/type: yes/0
Extra: 010db16352f1b8f43b4d86f9ed70bdf62839d812e959f4eba44ada7cfc60e56d1b0211000000868a2ee0d9000000000000000000

1 output(s) for total of 251.550604560000 dcy

stealth address amount amount idx
00: 520c270fb6df70c4a1b42df0e45a6ba83a6a3b26d940e6f8c343b0368105827a 251.550604560000 200015 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": 116928, "vin": [ { "gen": { "height": 116918 } } ], "vout": [ { "amount": 251550604560, "target": { "key": "520c270fb6df70c4a1b42df0e45a6ba83a6a3b26d940e6f8c343b0368105827a" } } ], "extra": [ 1, 13, 177, 99, 82, 241, 184, 244, 59, 77, 134, 249, 237, 112, 189, 246, 40, 57, 216, 18, 233, 89, 244, 235, 164, 74, 218, 124, 252, 96, 229, 109, 27, 2, 17, 0, 0, 0, 134, 138, 46, 224, 217, 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