Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ba84534a3aa877c38f2ead269912cab62ff4fefa4c72970b4b0911aeb38c4ca

Tx prefix hash: bdc26bbe41f0eaa327daee41f7dd3b577bfc44f12e9d4c4e8dc348e6d48e6356
Tx public key: 2fb2336fcf15b8b473c75ec8780189672142b84ac36b43e42f94a247183e24ca
Timestamp: 1582035915 Timestamp [UCT]: 2020-02-18 14:25:15 Age [y:d:h:m:s]: 05:260:19:28:28
Block: 67543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1337164 RingCT/type: yes/0
Extra: 012fb2336fcf15b8b473c75ec8780189672142b84ac36b43e42f94a247183e24ca02110000000212c4732d000000000000000000

1 output(s) for total of 366.608736167000 dcy

stealth address amount amount idx
00: 1757c0c9f4d2023755f64364367bd01ffe8077aebffa685c2406d0ebfe5347d1 366.608736167000 124410 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": 67553, "vin": [ { "gen": { "height": 67543 } } ], "vout": [ { "amount": 366608736167, "target": { "key": "1757c0c9f4d2023755f64364367bd01ffe8077aebffa685c2406d0ebfe5347d1" } } ], "extra": [ 1, 47, 178, 51, 111, 207, 21, 184, 180, 115, 199, 94, 200, 120, 1, 137, 103, 33, 66, 184, 74, 195, 107, 67, 228, 47, 148, 162, 71, 24, 62, 36, 202, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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