Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3a8b1d67a854904556c60cbe69b86075d07bf07d9f0c0213c6f3b55cd5c937d

Tx prefix hash: 3cb1f2b25a25ddeab518fdccaf809ccbf9680dde26a49de5f1aed0cb36dce256
Tx public key: c9165ac02c38852e6fbef51b9edb416f7779e212a19b73b91e70f1a7361a1a29
Timestamp: 1639250084 Timestamp [UCT]: 2021-12-11 19:14:44 Age [y:d:h:m:s]: 03:094:05:30:43
Block: 393387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 846100 RingCT/type: yes/0
Extra: 01c9165ac02c38852e6fbef51b9edb416f7779e212a19b73b91e70f1a7361a1a2902110000000cde12510f000000000000000000

1 output(s) for total of 30.517287377000 dcy

stealth address amount amount idx
00: b843a031ac1966347b994f6c071c337064ed41bafd93828fd9a56d727453f847 30.517287377000 790606 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": 393397, "vin": [ { "gen": { "height": 393387 } } ], "vout": [ { "amount": 30517287377, "target": { "key": "b843a031ac1966347b994f6c071c337064ed41bafd93828fd9a56d727453f847" } } ], "extra": [ 1, 201, 22, 90, 192, 44, 56, 133, 46, 111, 190, 245, 27, 158, 219, 65, 111, 119, 121, 226, 18, 161, 155, 115, 185, 30, 112, 241, 167, 54, 26, 26, 41, 2, 17, 0, 0, 0, 12, 222, 18, 81, 15, 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