Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cb5dc039e35c75b43c3cba3845f77b0e09b3823419df63fda12074b1727bffc

Tx prefix hash: b14c624b97c8be200487f836dac08cf3be99d71b008e29114f42cecb40da00dc
Tx public key: 55863efee4f54e62cff0c3212f1a4ab366e15587a46fd853a32fd33fa0a85cf0
Timestamp: 1702711091 Timestamp [UCT]: 2023-12-16 07:18:11 Age [y:d:h:m:s]: 01:134:14:30:30
Block: 914218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357360 RingCT/type: yes/0
Extra: 0155863efee4f54e62cff0c3212f1a4ab366e15587a46fd853a32fd33fa0a85cf002110000000afaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26c909ec1efe93d12fe9d22d10c14f5cea51ee899aef7afdd67597f144dd8661 0.600000000000 1371504 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": 914228, "vin": [ { "gen": { "height": 914218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26c909ec1efe93d12fe9d22d10c14f5cea51ee899aef7afdd67597f144dd8661" } } ], "extra": [ 1, 85, 134, 62, 254, 228, 245, 78, 98, 207, 240, 195, 33, 47, 26, 74, 179, 102, 225, 85, 135, 164, 111, 216, 83, 163, 47, 211, 63, 160, 168, 92, 240, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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