Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bbeae0aae054dbef3f51e592d5ec5311631c7426cc6bfdcd1924a8675b9ccc5

Tx prefix hash: 4b79e57cdb64914f0e9460f5a17f355cc6715de35fd97b0d0e858b7710a7d248
Tx public key: b0858710344a05e5bb70a11dac1647633c7d1c6cca66b0fa9c544a1b47f6afac
Timestamp: 1708247035 Timestamp [UCT]: 2024-02-18 09:03:55 Age [y:d:h:m:s]: 00:269:01:54:55
Block: 960117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192651 RingCT/type: yes/0
Extra: 01b0858710344a05e5bb70a11dac1647633c7d1c6cca66b0fa9c544a1b47f6afac0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d9a319cdf4e97822236bc0004aa170dd93a0413f6825613aee68c08df797688 0.600000000000 1419678 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": 960127, "vin": [ { "gen": { "height": 960117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d9a319cdf4e97822236bc0004aa170dd93a0413f6825613aee68c08df797688" } } ], "extra": [ 1, 176, 133, 135, 16, 52, 74, 5, 229, 187, 112, 161, 29, 172, 22, 71, 99, 60, 125, 28, 108, 202, 102, 176, 250, 156, 84, 74, 27, 71, 246, 175, 172, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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