Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222e16eeade658ea0c0741ef80e819a2b2ea97e0d0fcbda7d2db305f3e07a97f

Tx prefix hash: ddf4fef188b1c741025c285ea5d88c986ff2455f7785da0406173a44f7549afe
Tx public key: 37f213f8c7f243399bec261f37e6b93acf37a6e8dd0edf157b44beb8884e7dba
Timestamp: 1741197495 Timestamp [UCT]: 2025-03-05 17:58:15 Age [y:d:h:m:s]: 00:265:20:45:16
Block: 1232832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187768 RingCT/type: yes/0
Extra: 0137f213f8c7f243399bec261f37e6b93acf37a6e8dd0edf157b44beb8884e7dba0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49e5d661815e030da4e296d648fc69450162dd6dbfc52903b01de2fe8b5e1dc4 0.600000000000 1719747 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": 1232842, "vin": [ { "gen": { "height": 1232832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49e5d661815e030da4e296d648fc69450162dd6dbfc52903b01de2fe8b5e1dc4" } } ], "extra": [ 1, 55, 242, 19, 248, 199, 242, 67, 57, 155, 236, 38, 31, 55, 230, 185, 58, 207, 55, 166, 232, 221, 14, 223, 21, 123, 68, 190, 184, 136, 78, 125, 186, 2, 17, 0, 0, 0, 2, 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