Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aff396e16da18f65002c1e475f5033f7078dedac8a7e0cd636f28982bc95b49

Tx prefix hash: f7abdbf995ca0431a488a72270d20421a20884cc65c0e01c5b712c11a2431a94
Tx public key: 03a8123e90ed11d614692b217fd6018dce489525a1139d05b41b267c7c1743f5
Timestamp: 1698288064 Timestamp [UTC]: 2023-10-26 02:41:04 Age [y:d:h:m:s]: 02:124:09:38:45
Block: 877765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608300 RingCT/type: yes/0
Extra: 0103a8123e90ed11d614692b217fd6018dce489525a1139d05b41b267c7c1743f50211000000034b8f5122000000000000000000

1 output(s) for total of 0.000757879558 xmr

stealth address amount amount idx tag
00: f5691c780673b201ff45a98387fa0e039cc6636f12e79baa996a173753ff76fd 0.000757879558 1333153 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 dinastycoin-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": 877775, "vin": [ { "gen": { "height": 877765 } } ], "vout": [ { "amount": 757879558, "target": { "key": "f5691c780673b201ff45a98387fa0e039cc6636f12e79baa996a173753ff76fd" } } ], "extra": [ 1, 3, 168, 18, 62, 144, 237, 17, 214, 20, 105, 43, 33, 127, 214, 1, 141, 206, 72, 149, 37, 161, 19, 157, 5, 180, 27, 38, 124, 124, 23, 67, 245, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369