Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8ee08b82a9379b58de3652e0a8e515b0f02881f9f19c9118478657cc092beaf

Tx prefix hash: 00ce65c65567689df8c6c5fb2273b2ce5363b1421485ffaa7642adab8aa03277
Tx public key: 5d6a9675f0c4c2585f3defb9148f48fbb9669febe67f1cf8a553f2e7ff809cf2
Timestamp: 1707480635 Timestamp [UCT]: 2024-02-09 12:10:35 Age [y:d:h:m:s]: 00:225:02:05:45
Block: 953759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161238 RingCT/type: yes/0
Extra: 015d6a9675f0c4c2585f3defb9148f48fbb9669febe67f1cf8a553f2e7ff809cf202110000000a10a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45adbde119aabd5dd143cad4e190bd67396c6bd4a6931cd8f1632368c9be50e1 0.600000000000 1413005 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": 953769, "vin": [ { "gen": { "height": 953759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45adbde119aabd5dd143cad4e190bd67396c6bd4a6931cd8f1632368c9be50e1" } } ], "extra": [ 1, 93, 106, 150, 117, 240, 196, 194, 88, 95, 61, 239, 185, 20, 143, 72, 251, 185, 102, 159, 235, 230, 127, 28, 248, 165, 83, 242, 231, 255, 128, 156, 242, 2, 17, 0, 0, 0, 10, 16, 161, 116, 143, 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