Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b188427e7513cf9efccb466d3c47314e4d56dd2256d873ce4893747a233d67c7

Tx prefix hash: 20b6f1938bedb59b0c995d760600293d7526d243f56e5aad7fc1b15dfaeb631b
Tx public key: e21d5c2facb44e63efad4f4c2641f7fb80441dcf62b80ba95e7c29c58dd7792c
Timestamp: 1703409303 Timestamp [UCT]: 2023-12-24 09:15:03 Age [y:d:h:m:s]: 01:143:10:09:04
Block: 920015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363645 RingCT/type: yes/0
Extra: 01e21d5c2facb44e63efad4f4c2641f7fb80441dcf62b80ba95e7c29c58dd7792c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a14da8cd2063bf4e5b0ad91c1742c278858d1c0e43e73cb43dcdd52ec54c2c39 0.600000000000 1377693 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": 920025, "vin": [ { "gen": { "height": 920015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a14da8cd2063bf4e5b0ad91c1742c278858d1c0e43e73cb43dcdd52ec54c2c39" } } ], "extra": [ 1, 226, 29, 92, 47, 172, 180, 78, 99, 239, 173, 79, 76, 38, 65, 247, 251, 128, 68, 29, 207, 98, 184, 11, 169, 94, 124, 41, 197, 141, 215, 121, 44, 2, 17, 0, 0, 0, 1, 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