Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4964aff16c94152d9dda7f72a017fae833b4e7774a785d0bdb0532252a62c8ad

Tx prefix hash: a6c1f3c564fdc0ce942c9cd31ca8509f5f6b7beba406c4d2b9b8537d5d7b4498
Tx public key: 6eef9b1ad8e5528b51a1d5c97a06327338c59a0a50976fd0dced48cecb463d13
Timestamp: 1641396062 Timestamp [UTC]: 2022-01-05 15:21:02 Age [y:d:h:m:s]: 04:321:17:20:36
Block: 410967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1272527 RingCT/type: yes/0
Extra: 016eef9b1ad8e5528b51a1d5c97a06327338c59a0a50976fd0dced48cecb463d1302110000000137cb3088000000000000000000

1 output(s) for total of 0.026686773144 xmr

stealth address amount amount idx tag
00: 3869559851969f0241a5e252eac6da8c91c516337b9cd8261bd7955a2119a33d 0.026686773144 814225 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": 410977, "vin": [ { "gen": { "height": 410967 } } ], "vout": [ { "amount": 26686773144, "target": { "key": "3869559851969f0241a5e252eac6da8c91c516337b9cd8261bd7955a2119a33d" } } ], "extra": [ 1, 110, 239, 155, 26, 216, 229, 82, 139, 81, 161, 213, 201, 122, 6, 50, 115, 56, 197, 154, 10, 80, 151, 111, 208, 220, 237, 72, 206, 203, 70, 61, 19, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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: