Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82bd55eaabbd73177d458bf005e155fd0586fc4f2c6b0b2f8dabb1aa8a105f9d

Tx prefix hash: f3aebeb944606db7d43ce48d072ea2db064551371a07b4b875df596a0993d4de
Tx public key: 0b1ded3be9d63e9110e474a47d91226358bc56705cf564219ffbb258399adc48
Timestamp: 1592760707 Timestamp [UCT]: 2020-06-21 17:31:47 Age [y:d:h:m:s]: 04:232:19:34:02
Block: 110094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104718 RingCT/type: yes/0
Extra: 010b1ded3be9d63e9110e474a47d91226358bc56705cf564219ffbb258399adc4802110000000846a11e8a000000000000000000

1 output(s) for total of 264.980322125000 dcy

stealth address amount amount idx
00: ee75d3825bf316adc8a9d2543671802056739fd3a5de1246ec5a60e945a716d2 264.980322125000 190718 of 0

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": 110104, "vin": [ { "gen": { "height": 110094 } } ], "vout": [ { "amount": 264980322125, "target": { "key": "ee75d3825bf316adc8a9d2543671802056739fd3a5de1246ec5a60e945a716d2" } } ], "extra": [ 1, 11, 29, 237, 59, 233, 214, 62, 145, 16, 228, 116, 164, 125, 145, 34, 99, 88, 188, 86, 112, 92, 245, 100, 33, 159, 251, 178, 88, 57, 154, 220, 72, 2, 17, 0, 0, 0, 8, 70, 161, 30, 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