Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c63e97f0020ea26b7bbd6f6a3ba32c0e8682678f99aea29e8b9a50e59ac00cd

Tx prefix hash: 77dfa8b703a0c7bedb3c14e3b9da1a0c66a58aa72375b55496b3e2750b710f41
Tx public key: 079252a18f92117c68093250f21093fb4b3341b3a9dcf637e07d9b0ba2cbeb3f
Timestamp: 1737072870 Timestamp [UCT]: 2025-01-17 00:14:30 Age [y:d:h:m:s]: 00:303:09:20:06
Block: 1198941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214350 RingCT/type: yes/0
Extra: 01079252a18f92117c68093250f21093fb4b3341b3a9dcf637e07d9b0ba2cbeb3f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98888593241f29c8b327eb5f69804b4804926f9c6c37a03a9dd2d53023d4e4a3 0.600000000000 1685568 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": 1198951, "vin": [ { "gen": { "height": 1198941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98888593241f29c8b327eb5f69804b4804926f9c6c37a03a9dd2d53023d4e4a3" } } ], "extra": [ 1, 7, 146, 82, 161, 143, 146, 17, 124, 104, 9, 50, 80, 242, 16, 147, 251, 75, 51, 65, 179, 169, 220, 246, 55, 224, 125, 155, 11, 162, 203, 235, 63, 2, 17, 0, 0, 0, 5, 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