Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497da90440842a3c0d446e7233faf7169a51fe70dcf8e5d04dc3a112f4dd1d9e

Tx prefix hash: f52138128b8134e98cb574c2765db6e9a677643acbaeabb82ccbe3b78f411a81
Tx public key: f677fab74980763e05c621f493b6eef36595dd2ba78518215df69af2ec995818
Timestamp: 1771726531 Timestamp [UTC]: 2026-02-22 02:15:31 Age [y:d:h:m:s]: 00:270:09:55:53
Block: 1483041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198838 RingCT/type: yes/0
Extra: 01f677fab74980763e05c621f493b6eef36595dd2ba78518215df69af2ec995818021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd78d17523ee2a28640f9a3dca7770be87ac6d0f36821fd348f0dd80a4ff049b 0.000600000000 1972445 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": 1483051, "vin": [ { "gen": { "height": 1483041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd78d17523ee2a28640f9a3dca7770be87ac6d0f36821fd348f0dd80a4ff049b" } } ], "extra": [ 1, 246, 119, 250, 183, 73, 128, 118, 62, 5, 198, 33, 244, 147, 182, 238, 243, 101, 149, 221, 43, 167, 133, 24, 33, 93, 246, 154, 242, 236, 153, 88, 24, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: