Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d491776559f6231871a6bf825f819e6f980eec1d8c4a3858f6306af057f18abe

Tx prefix hash: 7651d3e2893c9d3e8ebf381ce8a603a5d9f4234092aa713f39cebd247e9c7bdc
Tx public key: 2907ff74f8ca359e28eaf8f17fb349254666d310032bd210b8596cd6c0ad7f16
Timestamp: 1727136492 Timestamp [UCT]: 2024-09-24 00:08:12 Age [y:d:h:m:s]: 00:151:22:37:41
Block: 1116717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108374 RingCT/type: yes/0
Extra: 012907ff74f8ca359e28eaf8f17fb349254666d310032bd210b8596cd6c0ad7f16021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ccc7495c5b0193160376cc5ed9e2c8034efe8a43cfd3ff5e2b8e274d90fc344 0.600000000000 1597298 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": 1116727, "vin": [ { "gen": { "height": 1116717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ccc7495c5b0193160376cc5ed9e2c8034efe8a43cfd3ff5e2b8e274d90fc344" } } ], "extra": [ 1, 41, 7, 255, 116, 248, 202, 53, 158, 40, 234, 248, 241, 127, 179, 73, 37, 70, 102, 211, 16, 3, 43, 210, 16, 184, 89, 108, 214, 192, 173, 127, 22, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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