Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3fd0d0fc3638d17728e5d15da31f99439ea23270f6ba8f8328d69e0acdc3169

Tx prefix hash: 0c4a0cc94e9ac9fbc8b5f9aeaa7885b6560f95a7d2bb92bed286b80776044ce4
Tx public key: 19cdb3423f0f0ac9192a64b478ee53777caa599087df6f365542399cf58cd82b
Timestamp: 1715197470 Timestamp [UCT]: 2024-05-08 19:44:30 Age [y:d:h:m:s]: 01:183:12:58:30
Block: 1017752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389788 RingCT/type: yes/0
Extra: 0119cdb3423f0f0ac9192a64b478ee53777caa599087df6f365542399cf58cd82b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34e509968c023dd12736ac15ef6e08a0047beecdba6f0c463913f595b7f1a3de 0.600000000000 1481537 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": 1017762, "vin": [ { "gen": { "height": 1017752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34e509968c023dd12736ac15ef6e08a0047beecdba6f0c463913f595b7f1a3de" } } ], "extra": [ 1, 25, 205, 179, 66, 63, 15, 10, 201, 25, 42, 100, 180, 120, 238, 83, 119, 124, 170, 89, 144, 135, 223, 111, 54, 85, 66, 57, 156, 245, 140, 216, 43, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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