Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b29b7a6a0293a0efcaa3a3ae5714e86d94bc3a1850d15b32f4d4ae2e88ca7e18

Tx prefix hash: 173c1b97e82ff669621f08d7e62be4b6838ca11c98db679ed898a455b8462509
Tx public key: a74693eecf496406149f9cc57c2137be0fe4f06b86465608b27a507338288a26
Timestamp: 1751131391 Timestamp [UTC]: 2025-06-28 17:23:11 Age [y:d:h:m:s]: 01:144:00:58:55
Block: 1314660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367405 RingCT/type: yes/0
Extra: 01a74693eecf496406149f9cc57c2137be0fe4f06b86465608b27a507338288a26021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d549a641f53331b7f929a1ae2cbcc9a633a5578550438960f6e565dc43e5a4e2 0.000600000000 1802311 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": 1314670, "vin": [ { "gen": { "height": 1314660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d549a641f53331b7f929a1ae2cbcc9a633a5578550438960f6e565dc43e5a4e2" } } ], "extra": [ 1, 167, 70, 147, 238, 207, 73, 100, 6, 20, 159, 156, 197, 124, 33, 55, 190, 15, 228, 240, 107, 134, 70, 86, 8, 178, 122, 80, 115, 56, 40, 138, 38, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: