Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abe7b9d706d4a9947048f9a0638ecb1ddcd21e97b9129c8d41ee375c56384782

Tx prefix hash: c6ac48023f8d01f2ed28eeff70082bcafde60a471b9f49b1f8f965b234dd868e
Tx public key: 89c72cb261cee721e17c770b112108bfc95ee8c87c31f3c4584546482c9a2e5b
Timestamp: 1736319206 Timestamp [UCT]: 2025-01-08 06:53:26 Age [y:d:h:m:s]: 00:089:15:49:13
Block: 1192707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63853 RingCT/type: yes/0
Extra: 0189c72cb261cee721e17c770b112108bfc95ee8c87c31f3c4584546482c9a2e5b02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 120aba3e377ade7a7277b762f9c10824d223ac2a712d1aaec358923389a4c194 0.600000000000 1679262 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": 1192717, "vin": [ { "gen": { "height": 1192707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "120aba3e377ade7a7277b762f9c10824d223ac2a712d1aaec358923389a4c194" } } ], "extra": [ 1, 137, 199, 44, 178, 97, 206, 231, 33, 225, 124, 119, 11, 17, 33, 8, 191, 201, 94, 232, 200, 124, 49, 243, 196, 88, 69, 70, 72, 44, 154, 46, 91, 2, 17, 0, 0, 0, 11, 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