Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cdb1df96f92d43638cd911552e0f0801d9920b33329bdb5f208ae8e2dc69706

Tx prefix hash: ca3b9554a4d6a9ab40d731e413c5c798c5bf52638078639eb192b9529564997e
Tx public key: aa8b12ff1c200ed9c0458e46011ce4bfea5fa76bf03a2283e592442407f81fb8
Timestamp: 1710572481 Timestamp [UCT]: 2024-03-16 07:01:21 Age [y:d:h:m:s]: 00:302:08:37:53
Block: 979420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216416 RingCT/type: yes/0
Extra: 01aa8b12ff1c200ed9c0458e46011ce4bfea5fa76bf03a2283e592442407f81fb80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f3a9983dd72382603ca3ee8715e571bbc43ae70ece9e73ae9f952cc47acf4d0 0.600000000000 1439453 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": 979430, "vin": [ { "gen": { "height": 979420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f3a9983dd72382603ca3ee8715e571bbc43ae70ece9e73ae9f952cc47acf4d0" } } ], "extra": [ 1, 170, 139, 18, 255, 28, 32, 14, 217, 192, 69, 142, 70, 1, 28, 228, 191, 234, 95, 167, 107, 240, 58, 34, 131, 229, 146, 68, 36, 7, 248, 31, 184, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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