Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a335eecda8155f8a4c5c98180459c6299236ab9bf5597b76c834c16040da23f

Tx prefix hash: bb6d7c0350a351a1527a86b3dc19eb1003e638e9f24e577b2ff55d454664ae7d
Tx public key: 8f0720a27d790217cfd85c622b2edf18ae6c79f565a37e92c5dad4d1b68794de
Timestamp: 1621870934 Timestamp [UCT]: 2021-05-24 15:42:14 Age [y:d:h:m:s]: 03:262:09:37:55
Block: 266243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 949637 RingCT/type: yes/0
Extra: 018f0720a27d790217cfd85c622b2edf18ae6c79f565a37e92c5dad4d1b68794de02110000000e6e2c823c000000000000000000

1 output(s) for total of 80.505760609000 dcy

stealth address amount amount idx
00: 03b5dc9d1ff12c4f056ab89a6144a90ce9ea3903aab84502ce0abf80d31a2e7c 80.505760609000 559469 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": 266253, "vin": [ { "gen": { "height": 266243 } } ], "vout": [ { "amount": 80505760609, "target": { "key": "03b5dc9d1ff12c4f056ab89a6144a90ce9ea3903aab84502ce0abf80d31a2e7c" } } ], "extra": [ 1, 143, 7, 32, 162, 125, 121, 2, 23, 207, 216, 92, 98, 43, 46, 223, 24, 174, 108, 121, 245, 101, 163, 126, 146, 197, 218, 212, 209, 182, 135, 148, 222, 2, 17, 0, 0, 0, 14, 110, 44, 130, 60, 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