Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29b751432fc79453664f8486b42951df51d42bd7397a1516302cbb5712c09792

Tx prefix hash: ef66d29b5ca24d12c00f742268ec307be2d29550aeb9900c123f8e6146a0a1bc
Tx public key: 41be1e854d5e7a58330f6d5eeb5bd7b32b1c3cb461ce6e9397da311e464c3b4a
Timestamp: 1745023866 Timestamp [UCT]: 2025-04-19 00:51:06 Age [y:d:h:m:s]: 00:044:22:04:42
Block: 1264507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32141 RingCT/type: yes/0
Extra: 0141be1e854d5e7a58330f6d5eeb5bd7b32b1c3cb461ce6e9397da311e464c3b4a0211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bff0c21d3587339317bdb8a056d7726ea4b709fdd9760eec030bc1ed749e9ab 0.600000000000 1751704 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": 1264517, "vin": [ { "gen": { "height": 1264507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bff0c21d3587339317bdb8a056d7726ea4b709fdd9760eec030bc1ed749e9ab" } } ], "extra": [ 1, 65, 190, 30, 133, 77, 94, 122, 88, 51, 15, 109, 94, 235, 91, 215, 179, 43, 28, 60, 180, 97, 206, 110, 147, 151, 218, 49, 30, 70, 76, 59, 74, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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