Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5ee0834ef58828bba5e25dd9335a42e55e394a2135dd808f0362722f48554ac

Tx prefix hash: 32f3b09f5f998a93152cb6701e91c0f45184e1d2574913d283f8341cb9e5e6db
Tx public key: 0f610c8a883a3b30cefc0f155dc70176773b9a27331dcb345ce5b350a6d7dbd4
Timestamp: 1741035256 Timestamp [UCT]: 2025-03-03 20:54:16 Age [y:d:h:m:s]: 00:262:01:33:43
Block: 1231486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185044 RingCT/type: yes/0
Extra: 010f610c8a883a3b30cefc0f155dc70176773b9a27331dcb345ce5b350a6d7dbd4021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a20438ab5db2b795f10fdeffe4f926734cd44d43556469f8e7a31fd4966c6ec4 0.600000000000 1718393 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": 1231496, "vin": [ { "gen": { "height": 1231486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a20438ab5db2b795f10fdeffe4f926734cd44d43556469f8e7a31fd4966c6ec4" } } ], "extra": [ 1, 15, 97, 12, 138, 136, 58, 59, 48, 206, 252, 15, 21, 93, 199, 1, 118, 119, 59, 154, 39, 51, 29, 203, 52, 92, 229, 179, 80, 166, 215, 219, 212, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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