Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68499f174f36df749762f1200088ed0b26fef4580c26c2c3ca09f2f6b7fcb344

Tx prefix hash: 557affbdb9abebb11dacfc38a48ec0f7e5814077608708d6be1c368e1a98c714
Tx public key: 2ee368ef9edbd3c1d74993d0c6296bf0abed48ab39f5a62e3bff1d82c7c37dc1
Timestamp: 1763905305 Timestamp [UCT]: 2025-11-23 13:41:45 Age [y:d:h:m:s]: 00:004:05:08:30
Block: 1418420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3033 RingCT/type: yes/0
Extra: 012ee368ef9edbd3c1d74993d0c6296bf0abed48ab39f5a62e3bff1d82c7c37dc10211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dbf45653a1d39bb8f8f794ee99cd0d3a6a0bc5c25b49bba069643e063527093 0.600000000000 1906951 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": 1418430, "vin": [ { "gen": { "height": 1418420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dbf45653a1d39bb8f8f794ee99cd0d3a6a0bc5c25b49bba069643e063527093" } } ], "extra": [ 1, 46, 227, 104, 239, 158, 219, 211, 193, 215, 73, 147, 208, 198, 41, 107, 240, 171, 237, 72, 171, 57, 245, 166, 46, 59, 255, 29, 130, 199, 195, 125, 193, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 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