Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86abe44372c24764fe29ced52af1a6079f11d2afedfff946512b83021a9408f5

Tx prefix hash: 248cc8d9192460ab6f2b6e531e352e0995dea0c4940fd5238ad4e7a0897c1eaf
Tx public key: 823226a26bfe0f1dce447847e4f763aea67c27f31984cc8314c07e5d3dab978d
Timestamp: 1740313335 Timestamp [UCT]: 2025-02-23 12:22:15 Age [y:d:h:m:s]: 00:227:10:22:20
Block: 1225493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160256 RingCT/type: yes/0
Extra: 01823226a26bfe0f1dce447847e4f763aea67c27f31984cc8314c07e5d3dab978d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 014d45d26d4d60c88558da82ccc34d6ba466fea2c94a2de2631922c10f4fd258 0.600000000000 1712358 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": 1225503, "vin": [ { "gen": { "height": 1225493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "014d45d26d4d60c88558da82ccc34d6ba466fea2c94a2de2631922c10f4fd258" } } ], "extra": [ 1, 130, 50, 38, 162, 107, 254, 15, 29, 206, 68, 120, 71, 228, 247, 99, 174, 166, 124, 39, 243, 25, 132, 204, 131, 20, 192, 126, 93, 61, 171, 151, 141, 2, 17, 0, 0, 0, 3, 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