Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 993e0d0a9a03d6d9426edc2872a6c1c5c66d9c07c0a5fa17939a9fd56a4ddbdc

Tx prefix hash: aa26b3cacd726d74c0c412cb8dc7e5a5b7631102cc4eefce432173af3cda62a5
Tx public key: 736caf17e9b8faf63dd592ae22f9e9c4af1e58b40a455fa2cdde54c2116f833a
Timestamp: 1712037607 Timestamp [UCT]: 2024-04-02 06:00:07 Age [y:d:h:m:s]: 01:023:15:48:44
Block: 991515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277911 RingCT/type: yes/0
Extra: 01736caf17e9b8faf63dd592ae22f9e9c4af1e58b40a455fa2cdde54c2116f833a02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1351a39758bc0cb40a7013f7f9ef0820caa30b002a46e17e9ce38037623156f0 0.600000000000 1451851 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": 991525, "vin": [ { "gen": { "height": 991515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1351a39758bc0cb40a7013f7f9ef0820caa30b002a46e17e9ce38037623156f0" } } ], "extra": [ 1, 115, 108, 175, 23, 233, 184, 250, 246, 61, 213, 146, 174, 34, 249, 233, 196, 175, 30, 88, 180, 10, 69, 95, 162, 205, 222, 84, 194, 17, 111, 131, 58, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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