Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5db461aeee0729115647f9e45dde9ea3cf5bf1a78d1d7fb24d69309bab27e334

Tx prefix hash: eba6b50a72ea65a22f6afb8386a1538c34379d40add52a7624437d2fa6409ead
Tx public key: 7232e22af2574fc582a29f062c915a1699492cf54d2cb36a5e7df196c1dfd159
Timestamp: 1736698281 Timestamp [UCT]: 2025-01-12 16:11:21 Age [y:d:h:m:s]: 00:075:10:53:57
Block: 1195854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53697 RingCT/type: yes/0
Extra: 017232e22af2574fc582a29f062c915a1699492cf54d2cb36a5e7df196c1dfd1590211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6082fd9e75417388dbf1e7ee1b0389adf69441f7f75abd9164ba43236293da3 0.600000000000 1682447 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": 1195864, "vin": [ { "gen": { "height": 1195854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6082fd9e75417388dbf1e7ee1b0389adf69441f7f75abd9164ba43236293da3" } } ], "extra": [ 1, 114, 50, 226, 42, 242, 87, 79, 197, 130, 162, 159, 6, 44, 145, 90, 22, 153, 73, 44, 245, 77, 44, 179, 106, 94, 125, 241, 150, 193, 223, 209, 89, 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