Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaf82363dfba597825dc75e74ce6e24d6747f6d5ce8d28813bc463a2d6f49f14

Tx prefix hash: f3b1d8fc5b39335c0ad97ea25f1815eff76cae65626053723af5973c7b34d6cc
Tx public key: 078d4f292faf79200c11a7a560dfea694317f633b4237390ec7b477eb07bd84f
Timestamp: 1577766433 Timestamp [UCT]: 2019-12-31 04:27:13 Age [y:d:h:m:s]: 04:275:00:05:05
Block: 35464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085690 RingCT/type: yes/0
Extra: 01078d4f292faf79200c11a7a560dfea694317f633b4237390ec7b477eb07bd84f0211000000074ac5aa02000000000000000000

1 output(s) for total of 468.267374662000 dcy

stealth address amount amount idx
00: e8a4071fc07a1e94bc6e14d639aefc499c8cb85c96d09ab9672a447191664c4a 468.267374662000 59826 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": 35474, "vin": [ { "gen": { "height": 35464 } } ], "vout": [ { "amount": 468267374662, "target": { "key": "e8a4071fc07a1e94bc6e14d639aefc499c8cb85c96d09ab9672a447191664c4a" } } ], "extra": [ 1, 7, 141, 79, 41, 47, 175, 121, 32, 12, 17, 167, 165, 96, 223, 234, 105, 67, 23, 246, 51, 180, 35, 115, 144, 236, 123, 71, 126, 176, 123, 216, 79, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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