Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 573b72b9203d5b5cfbd78cad77014da33faafc75ee2f3451d68e570e501bd4a5

Tx prefix hash: 956459722fb4cf038e3a7c81b0517e8604ec259faee965e8085de23992956c5c
Tx public key: d1f070bb110b017a58da9fdf0e9f9d596a71d81fcb74040d5a24e40f5c58761c
Timestamp: 1579437815 Timestamp [UTC]: 2020-01-19 12:43:35 Age [y:d:h:m:s]: 06:030:23:47:38
Block: 48968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1430794 RingCT/type: yes/0
Extra: 01d1f070bb110b017a58da9fdf0e9f9d596a71d81fcb74040d5a24e40f5c58761c02110000000349b77a3d000000000000000000

1 output(s) for total of 0.422424912618 xmr

stealth address amount amount idx tag
00: b085421be21569262ec18032b2279599253d0b80a0e29e89f81ee1242286c218 0.422424912618 90816 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": 48978, "vin": [ { "gen": { "height": 48968 } } ], "vout": [ { "amount": 422424912618, "target": { "key": "b085421be21569262ec18032b2279599253d0b80a0e29e89f81ee1242286c218" } } ], "extra": [ 1, 209, 240, 112, 187, 17, 11, 1, 122, 88, 218, 159, 223, 14, 159, 157, 89, 106, 113, 216, 31, 203, 116, 4, 13, 90, 36, 228, 15, 92, 88, 118, 28, 2, 17, 0, 0, 0, 3, 73, 183, 122, 61, 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