Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bf793e69f8324200240a67407a8e781c19a54436c4e96950c33b237ff78af8b

Tx prefix hash: a62fa416307684755aeb9b92bef11047c4adb9efc3512c1d701a70332f32fdd5
Tx public key: a9e9d4d7235f8f6f2452d854b0365b8f968c24e6488bda9f7c5c1942f4d45baa
Timestamp: 1713701941 Timestamp [UCT]: 2024-04-21 12:19:01 Age [y:d:h:m:s]: 00:251:04:10:37
Block: 1005338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179789 RingCT/type: yes/0
Extra: 01a9e9d4d7235f8f6f2452d854b0365b8f968c24e6488bda9f7c5c1942f4d45baa0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40e8fb20194137316e513c44a84e89596406f4cb9b33c65c866ad8c018aefd7f 0.600000000000 1465946 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": 1005348, "vin": [ { "gen": { "height": 1005338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40e8fb20194137316e513c44a84e89596406f4cb9b33c65c866ad8c018aefd7f" } } ], "extra": [ 1, 169, 233, 212, 215, 35, 95, 143, 111, 36, 82, 216, 84, 176, 54, 91, 143, 150, 140, 36, 230, 72, 139, 218, 159, 124, 92, 25, 66, 244, 212, 91, 170, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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