Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c910ae98aef744205e488ee451a9893ab92fe445eebf9ce262e60379d1afeb0d

Tx prefix hash: aad7c981f1efb9a8aef1e1942db93cd7a275b70d539cf517930028ccc2886690
Tx public key: 635f4bd5b93fc257abc8471bf018e6977c0f292a6963fa7337c512876b5e8a47
Timestamp: 1634835211 Timestamp [UCT]: 2021-10-21 16:53:31 Age [y:d:h:m:s]: 03:040:07:36:03
Block: 357568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 807063 RingCT/type: yes/0
Extra: 01635f4bd5b93fc257abc8471bf018e6977c0f292a6963fa7337c512876b5e8a47021100000006fdc024ec000000000000000000

1 output(s) for total of 40.107832723000 dcy

stealth address amount amount idx
00: 0aec812a9155039d471b6b3c1289b7be4fb22215018bdfa6b9f2cf1bc6565b3b 40.107832723000 729060 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": 357578, "vin": [ { "gen": { "height": 357568 } } ], "vout": [ { "amount": 40107832723, "target": { "key": "0aec812a9155039d471b6b3c1289b7be4fb22215018bdfa6b9f2cf1bc6565b3b" } } ], "extra": [ 1, 99, 95, 75, 213, 185, 63, 194, 87, 171, 200, 71, 27, 240, 24, 230, 151, 124, 15, 41, 42, 105, 99, 250, 115, 55, 197, 18, 135, 107, 94, 138, 71, 2, 17, 0, 0, 0, 6, 253, 192, 36, 236, 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