Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea051ffaefaa927967cc3ee00d182f60a736b57ec854bd16951b5c4526d797b

Tx prefix hash: 0c75abf7d514a3d9a3cf793638810cb8ac0b96c39d56fc22f92fadb1d7b059da
Tx public key: 082af358b878f31bf4aa981699ade3064e61b7c1960e3790b9d77992dc851b9f
Timestamp: 1733254671 Timestamp [UCT]: 2024-12-03 19:37:51 Age [y:d:h:m:s]: 00:024:14:42:06
Block: 1167343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17605 RingCT/type: yes/0
Extra: 01082af358b878f31bf4aa981699ade3064e61b7c1960e3790b9d77992dc851b9f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a37e9900ba472f4e11ed4eaf5dd6d114783a9f4f24a3ecc7c23433692033b5e 0.600000000000 1653038 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": 1167353, "vin": [ { "gen": { "height": 1167343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a37e9900ba472f4e11ed4eaf5dd6d114783a9f4f24a3ecc7c23433692033b5e" } } ], "extra": [ 1, 8, 42, 243, 88, 184, 120, 243, 27, 244, 170, 152, 22, 153, 173, 227, 6, 78, 97, 183, 193, 150, 14, 55, 144, 185, 215, 121, 146, 220, 133, 27, 159, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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