Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a79278dbe88a44622438483b6d59add55583fdd95ffde7bed0eb05374c409c9f

Tx prefix hash: 203c196761d10973877b1b651bb46ea675898fec7d3643c7cf77d2c1859cc273
Tx public key: 56a87f56d4eadad3b19a88c9b5d3ae8c8e7e785662db7c6401266fa1e31a0bd3
Timestamp: 1725524263 Timestamp [UCT]: 2024-09-05 08:17:43 Age [y:d:h:m:s]: 00:079:23:31:09
Block: 1103355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57194 RingCT/type: yes/0
Extra: 0156a87f56d4eadad3b19a88c9b5d3ae8c8e7e785662db7c6401266fa1e31a0bd3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 696f4f49ff24b56b6cafc5e11abe8ad68d1ba771191ae832af4c46fe68a7daa2 0.600000000000 1580150 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": 1103365, "vin": [ { "gen": { "height": 1103355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "696f4f49ff24b56b6cafc5e11abe8ad68d1ba771191ae832af4c46fe68a7daa2" } } ], "extra": [ 1, 86, 168, 127, 86, 212, 234, 218, 211, 177, 154, 136, 201, 181, 211, 174, 140, 142, 126, 120, 86, 98, 219, 124, 100, 1, 38, 111, 161, 227, 26, 11, 211, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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