Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6303d1f9e51c8c2b33c4e3cce13c5c9a376cb16d8bd29dfb26eab161b3b2e26a

Tx prefix hash: 6b4f8b8f870a55818a10a282fc55e5ca831d963a1ffc48e6fbd1986a26abffc5
Tx public key: 229feec801bce12e177eb4ca17a7d4a2e2e396d5d8de4e41207daad06c566a43
Timestamp: 1658398054 Timestamp [UCT]: 2022-07-21 10:07:34 Age [y:d:h:m:s]: 02:284:11:39:37
Block: 548488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724506 RingCT/type: yes/0
Extra: 01229feec801bce12e177eb4ca17a7d4a2e2e396d5d8de4e41207daad06c566a4302110000000fd3fcec30000000000000000000

1 output(s) for total of 9.346127520000 dcy

stealth address amount amount idx
00: 22442e440c0940a08e23f964abe12bc0f645e1a87c6683480f86161baf01c388 9.346127520000 979747 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": 548498, "vin": [ { "gen": { "height": 548488 } } ], "vout": [ { "amount": 9346127520, "target": { "key": "22442e440c0940a08e23f964abe12bc0f645e1a87c6683480f86161baf01c388" } } ], "extra": [ 1, 34, 159, 238, 200, 1, 188, 225, 46, 23, 126, 180, 202, 23, 167, 212, 162, 226, 227, 150, 213, 216, 222, 78, 65, 32, 125, 170, 208, 108, 86, 106, 67, 2, 17, 0, 0, 0, 15, 211, 252, 236, 48, 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