Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac0fe09bd122abb46ba683d19326b38d8fc77478c7e041486a28c4b29fc04526

Tx prefix hash: a0a32f40528bc9d4f4d9cc5560e0851215c111539d16ce66430ebc3ab12a8dea
Tx public key: e39a252b21484695aee65a348dfcdc5f8ffa2d73a2aea0e46b317c4b94afc7f1
Timestamp: 1727957992 Timestamp [UCT]: 2024-10-03 12:19:52 Age [y:d:h:m:s]: 00:052:01:49:04
Block: 1123532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37206 RingCT/type: yes/0
Extra: 01e39a252b21484695aee65a348dfcdc5f8ffa2d73a2aea0e46b317c4b94afc7f1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f0a56c3edae5673eacdb06f86dc83320375db35312d4c7af859b9b8708ab6e1 0.600000000000 1606067 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": 1123542, "vin": [ { "gen": { "height": 1123532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f0a56c3edae5673eacdb06f86dc83320375db35312d4c7af859b9b8708ab6e1" } } ], "extra": [ 1, 227, 154, 37, 43, 33, 72, 70, 149, 174, 230, 90, 52, 141, 252, 220, 95, 143, 250, 45, 115, 162, 174, 160, 228, 107, 49, 124, 75, 148, 175, 199, 241, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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