Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a0fa3452cc3a492e3219b08573bebf69857507f331eb06f29000f8b9789df48

Tx prefix hash: 85f362b65f8caf1d7b6075fddec64f7c0fac619f6130a5e4be70b75cb27c18b9
Tx public key: c81cbb7b248d484b6293bd60ffb01b920f349d5884ae46ba20b949c389ae1c71
Timestamp: 1639408253 Timestamp [UCT]: 2021-12-13 15:10:53 Age [y:d:h:m:s]: 03:332:11:40:34
Block: 394697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1014097 RingCT/type: yes/0
Extra: 01c81cbb7b248d484b6293bd60ffb01b920f349d5884ae46ba20b949c389ae1c7102110000000176899486000000000000000000

1 output(s) for total of 30.213800111000 dcy

stealth address amount amount idx
00: 746b1baa7f8c463a1c1bd30eadb5139f14c6519aae42a30aa10b679db6507c25 30.213800111000 792380 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": 394707, "vin": [ { "gen": { "height": 394697 } } ], "vout": [ { "amount": 30213800111, "target": { "key": "746b1baa7f8c463a1c1bd30eadb5139f14c6519aae42a30aa10b679db6507c25" } } ], "extra": [ 1, 200, 28, 187, 123, 36, 141, 72, 75, 98, 147, 189, 96, 255, 176, 27, 146, 15, 52, 157, 88, 132, 174, 70, 186, 32, 185, 73, 195, 137, 174, 28, 113, 2, 17, 0, 0, 0, 1, 118, 137, 148, 134, 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