Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f390250062fc4be9d877ac43bb3abd9494f116d4045bb186bd91266c09931c73

Tx prefix hash: 7926fd3ddca9e7bef9ab45f3e5e86fb433ae8ee3919e0dcf140e8ba89baa56d9
Tx public key: 54c582a27f8276f63b8aa16cc430304705b37d87c20cd6a3b053b5ee07235817
Timestamp: 1702942371 Timestamp [UCT]: 2023-12-18 23:32:51 Age [y:d:h:m:s]: 01:182:16:32:33
Block: 916142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391619 RingCT/type: yes/0
Extra: 0154c582a27f8276f63b8aa16cc430304705b37d87c20cd6a3b053b5ee0723581702110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b828e5866a429231c9ae8e33314db9df282fc7cf6a65846eee819122e6f7557a 0.600000000000 1373620 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": 916152, "vin": [ { "gen": { "height": 916142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b828e5866a429231c9ae8e33314db9df282fc7cf6a65846eee819122e6f7557a" } } ], "extra": [ 1, 84, 197, 130, 162, 127, 130, 118, 246, 59, 138, 161, 108, 196, 48, 48, 71, 5, 179, 125, 135, 194, 12, 214, 163, 176, 83, 181, 238, 7, 35, 88, 23, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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