Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58da0477119052ffb3d2396ebb7e3d9b83311c4a238e3859d41f9cecb82f09f0

Tx prefix hash: 6fe499d0618d379b0cf3e75868478f4754cf7f848aaef2727013ae3e469ea24e
Tx public key: 1924eef219a85bf4e7d1fb4fc5ddc2dbe58301c9ae4563e38a71e43e0257437c
Timestamp: 1714971425 Timestamp [UCT]: 2024-05-06 04:57:05 Age [y:d:h:m:s]: 01:007:13:14:27
Block: 1015870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266326 RingCT/type: yes/0
Extra: 011924eef219a85bf4e7d1fb4fc5ddc2dbe58301c9ae4563e38a71e43e0257437c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26ac3b7a867ee3a9a33ec572ceaf30432d84c2486f036a4bd7db72a1a7b29151 0.600000000000 1479313 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": 1015880, "vin": [ { "gen": { "height": 1015870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26ac3b7a867ee3a9a33ec572ceaf30432d84c2486f036a4bd7db72a1a7b29151" } } ], "extra": [ 1, 25, 36, 238, 242, 25, 168, 91, 244, 231, 209, 251, 79, 197, 221, 194, 219, 229, 131, 1, 201, 174, 69, 99, 227, 138, 113, 228, 62, 2, 87, 67, 124, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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