Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3877fa9b067a83b47997f0db0c203fd740a2872f1c339df867fbf2d917d1793c

Tx prefix hash: 67c5d3193f7821cba2368583c661660f6ca3282eb0ac5e955eb31493af57d713
Tx public key: 50b0d15c0ee56e322c40f4dc59bda60c6e96180de931b9e0cf706fb15e5e9190
Timestamp: 1712820174 Timestamp [UCT]: 2024-04-11 07:22:54 Age [y:d:h:m:s]: 01:181:02:14:25
Block: 998007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388074 RingCT/type: yes/0
Extra: 0150b0d15c0ee56e322c40f4dc59bda60c6e96180de931b9e0cf706fb15e5e919002110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3461992ec9939ad87219adeed8a55d50ebf2144662ae2c1d992ac88b26ecae8b 0.600000000000 1458441 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": 998017, "vin": [ { "gen": { "height": 998007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3461992ec9939ad87219adeed8a55d50ebf2144662ae2c1d992ac88b26ecae8b" } } ], "extra": [ 1, 80, 176, 209, 92, 14, 229, 110, 50, 44, 64, 244, 220, 89, 189, 166, 12, 110, 150, 24, 13, 233, 49, 185, 224, 207, 112, 111, 177, 94, 94, 145, 144, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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