Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93b50ae70dbb1928e84d3b7e090b6d15c002f0ef8cd4be3f60130b278a421032

Tx prefix hash: 9ad2f3ef3151d3ede4e835fc5faa430d6172ab045b3d2c59af4e8494ea8fe5be
Tx public key: 817741dd969b201fdf884a6310494a2bb23c05ec204b08f1cb931364604fd044
Timestamp: 1677702365 Timestamp [UTC]: 2023-03-01 20:26:05 Age [y:d:h:m:s]: 03:266:23:22:19
Block: 707768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 976382 RingCT/type: yes/0
Extra: 01817741dd969b201fdf884a6310494a2bb23c05ec204b08f1cb931364604fd0440211000000075029cbac000000000000000000

1 output(s) for total of 0.002772494603 xmr

stealth address amount amount idx tag
00: 39f4a40f43759ca4d06722df5c8e17edcaa3615a9aebce5220ca58356742c870 0.002772494603 1151591 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": 707778, "vin": [ { "gen": { "height": 707768 } } ], "vout": [ { "amount": 2772494603, "target": { "key": "39f4a40f43759ca4d06722df5c8e17edcaa3615a9aebce5220ca58356742c870" } } ], "extra": [ 1, 129, 119, 65, 221, 150, 155, 32, 31, 223, 136, 74, 99, 16, 73, 74, 43, 178, 60, 5, 236, 32, 75, 8, 241, 203, 147, 19, 100, 96, 79, 208, 68, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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) | monero version: