Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cfa1f013f53f97cddd1031850c017c9349d224bbd05e60c2f8893d9c3715278

Tx prefix hash: 33239018d0c513c3272a687a21f9c06bf8274d423f070ed6a31d54bc09402d84
Tx public key: 8352bb29a394e5638daebd505c2871d765712bd61a1f0cb24c3dc195b8dc7e00
Timestamp: 1718574633 Timestamp [UCT]: 2024-06-16 21:50:33 Age [y:d:h:m:s]: 01:150:07:26:49
Block: 1045751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365982 RingCT/type: yes/0
Extra: 018352bb29a394e5638daebd505c2871d765712bd61a1f0cb24c3dc195b8dc7e000211000000023a272312000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f13923444066e071697f9bce55c4bc8f37b2b7790389500b9234c0e076bcb2ab 0.600000000000 1515414 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": 1045761, "vin": [ { "gen": { "height": 1045751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f13923444066e071697f9bce55c4bc8f37b2b7790389500b9234c0e076bcb2ab" } } ], "extra": [ 1, 131, 82, 187, 41, 163, 148, 229, 99, 141, 174, 189, 80, 92, 40, 113, 215, 101, 113, 43, 214, 26, 31, 12, 178, 76, 61, 193, 149, 184, 220, 126, 0, 2, 17, 0, 0, 0, 2, 58, 39, 35, 18, 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