Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce0da3266acfdf0327bb8e141e921aa79cc1fd66c9febb03a0e0fb8422a62626

Tx prefix hash: 6deea431763ff3018dfd3f1ed688cd833627a3204ee8bbd919fb0fd7daa14aff
Tx public key: eb54b3384a48d3503076607c5fca3885f2e8e394728aed58b6c35f9169bbec39
Timestamp: 1708107295 Timestamp [UCT]: 2024-02-16 18:14:55 Age [y:d:h:m:s]: 01:040:23:13:00
Block: 958954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290316 RingCT/type: yes/0
Extra: 01eb54b3384a48d3503076607c5fca3885f2e8e394728aed58b6c35f9169bbec390211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a04534266eaea33e94911a2ee095dc8baae4fd78826a8914b8056fe3b476f33 0.600000000000 1418425 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": 958964, "vin": [ { "gen": { "height": 958954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a04534266eaea33e94911a2ee095dc8baae4fd78826a8914b8056fe3b476f33" } } ], "extra": [ 1, 235, 84, 179, 56, 74, 72, 211, 80, 48, 118, 96, 124, 95, 202, 56, 133, 242, 232, 227, 148, 114, 138, 237, 88, 182, 195, 95, 145, 105, 187, 236, 57, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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