Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64afdcd4626ce7eb04873ce1d16ad9ba5b6d5148b41d3f3852f96fe1ed74a927

Tx prefix hash: 50814e2eef0079d3571241b08fc4e6e9a79f15c7b30d979d02c2249a1849f4b1
Tx public key: 78460c12286f5162c13ee73ae5f41af66226aa500f7755f67af1b3003baf1a93
Timestamp: 1756546266 Timestamp [UTC]: 2025-08-30 09:31:06 Age [y:d:h:m:s]: 00:261:16:01:07
Block: 1357582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179713 RingCT/type: yes/0
Extra: 0178460c12286f5162c13ee73ae5f41af66226aa500f7755f67af1b3003baf1a93021100000005b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 483a18669f206467e1dcfd92fac063fcf4bfff0b594b775a23d35358695f2d27 0.000600000000 1845591 of 15 -

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": 1357592, "vin": [ { "gen": { "height": 1357582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "483a18669f206467e1dcfd92fac063fcf4bfff0b594b775a23d35358695f2d27" } } ], "extra": [ 1, 120, 70, 12, 18, 40, 111, 81, 98, 193, 62, 231, 58, 229, 244, 26, 246, 98, 38, 170, 80, 15, 119, 85, 246, 122, 241, 179, 0, 59, 175, 26, 147, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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: