Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18b1ad057911d8f88a382367a5a69e34f56d97de56a1cbe59f13940e49ca1bb3

Tx prefix hash: cbf0fbeb19c3d27cfd017a6ab0495a950e94aceda13283384893b7f5e47ab0df
Tx public key: e520be147f4e9233f5f8b9f7718ac7515e72f5efbb7f2fcf536b2432602958e2
Timestamp: 1733608762 Timestamp [UCT]: 2024-12-07 21:59:22 Age [y:d:h:m:s]: 00:112:11:03:13
Block: 1170285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80157 RingCT/type: yes/0
Extra: 01e520be147f4e9233f5f8b9f7718ac7515e72f5efbb7f2fcf536b2432602958e2021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c333b98fc9c59bd8070d620150d43343a49a6056a362e520e3fa214197c0f95 0.600000000000 1656014 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": 1170295, "vin": [ { "gen": { "height": 1170285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c333b98fc9c59bd8070d620150d43343a49a6056a362e520e3fa214197c0f95" } } ], "extra": [ 1, 229, 32, 190, 20, 127, 78, 146, 51, 245, 248, 185, 247, 113, 138, 199, 81, 94, 114, 245, 239, 187, 127, 47, 207, 83, 107, 36, 50, 96, 41, 88, 226, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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