Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f536aa229ff4272271d29a9a789d404377078a66c2016b8cc647a2d52fd8bcd

Tx prefix hash: d7dd7c3d94d69d9b861144a6d3b875470bf518cec0a2e161cc663de31df9428f
Tx public key: e9af70d3b6f1648458848ccca6c2e471c868b9e27d3cc5c7f900aa33c095c8b4
Timestamp: 1736125870 Timestamp [UCT]: 2025-01-06 01:11:10 Age [y:d:h:m:s]: 00:164:13:33:36
Block: 1191117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117318 RingCT/type: yes/0
Extra: 01e9af70d3b6f1648458848ccca6c2e471c868b9e27d3cc5c7f900aa33c095c8b402110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 417da2e5a358f8ac8ec5326df474d8e1d1756f55f9daff607068c63d2c5bcfbb 0.600000000000 1677640 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": 1191127, "vin": [ { "gen": { "height": 1191117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "417da2e5a358f8ac8ec5326df474d8e1d1756f55f9daff607068c63d2c5bcfbb" } } ], "extra": [ 1, 233, 175, 112, 211, 182, 241, 100, 132, 88, 132, 140, 204, 166, 194, 228, 113, 200, 104, 185, 226, 125, 60, 197, 199, 249, 0, 170, 51, 192, 149, 200, 180, 2, 17, 0, 0, 0, 10, 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