Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d1f0ba0eb8b1e00cff6b8db0a194eb14a3fc7d6cb9466986ab3fbb08f38a585

Tx prefix hash: 48b95712b77484fd4822cac42312235b5c7aaf4d6ab555039082c458cd8e031e
Tx public key: 73e07ec90d11c50196457c25ac3ff953f2f9793f2117f31c4fb10ecc619984ec
Timestamp: 1738039514 Timestamp [UCT]: 2025-01-28 04:45:14 Age [y:d:h:m:s]: 00:143:10:56:01
Block: 1206703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102437 RingCT/type: yes/0
Extra: 0173e07ec90d11c50196457c25ac3ff953f2f9793f2117f31c4fb10ecc619984ec0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9510aa0b890adfdc7a1c3459925e989d0f96653ebb2dc1520ea32b57bf505db 0.600000000000 1693416 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": 1206713, "vin": [ { "gen": { "height": 1206703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9510aa0b890adfdc7a1c3459925e989d0f96653ebb2dc1520ea32b57bf505db" } } ], "extra": [ 1, 115, 224, 126, 201, 13, 17, 197, 1, 150, 69, 124, 37, 172, 63, 249, 83, 242, 249, 121, 63, 33, 23, 243, 28, 79, 177, 14, 204, 97, 153, 132, 236, 2, 17, 0, 0, 0, 7, 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