Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40ea9c0308a309f3ab407501ae243894cf21a55c44f66040c8e3756fd7acf69e

Tx prefix hash: c146802de9b1f53e35489e94386a135e495d86cff5918e0b5bc0a598f288fa5a
Tx public key: a202e87358d4f6d3cee8637f0beccfb099794f8f0939585b9da66b047bd91fb2
Timestamp: 1713279577 Timestamp [UCT]: 2024-04-16 14:59:37 Age [y:d:h:m:s]: 01:197:21:07:52
Block: 1001823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400092 RingCT/type: yes/0
Extra: 01a202e87358d4f6d3cee8637f0beccfb099794f8f0939585b9da66b047bd91fb202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 974f6bb4b3a2f608992175e7a8bf26fb38dac6971f3640bce001593ed84bb8d7 0.600000000000 1462335 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": 1001833, "vin": [ { "gen": { "height": 1001823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "974f6bb4b3a2f608992175e7a8bf26fb38dac6971f3640bce001593ed84bb8d7" } } ], "extra": [ 1, 162, 2, 232, 115, 88, 212, 246, 211, 206, 232, 99, 127, 11, 236, 207, 176, 153, 121, 79, 143, 9, 57, 88, 91, 157, 166, 107, 4, 123, 217, 31, 178, 2, 17, 0, 0, 0, 1, 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