Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d1f32bda384ba19505d0484db9dbd70ecc69e4c5db67f197651309c4686229a

Tx prefix hash: 8163c1059cb107166e92f7da34d3e46b5c247d944674d46332c36e5fbf71461c
Tx public key: 8c5c6512e24cc95fc0fce0e6f6944365225a108e65ba0aa0656e4ad5814342a3
Timestamp: 1769488101 Timestamp [UTC]: 2026-01-27 04:28:21 Age [y:d:h:m:s]: 00:298:16:48:22
Block: 1464511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218983 RingCT/type: yes/0
Extra: 018c5c6512e24cc95fc0fce0e6f6944365225a108e65ba0aa0656e4ad5814342a3021100000004215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6cad33e91a79d23a00d1e2ad6b0506b0260e69c413af5f96a113c3042ee9b738 0.000600000000 1953737 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": 1464521, "vin": [ { "gen": { "height": 1464511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cad33e91a79d23a00d1e2ad6b0506b0260e69c413af5f96a113c3042ee9b738" } } ], "extra": [ 1, 140, 92, 101, 18, 226, 76, 201, 95, 192, 252, 224, 230, 246, 148, 67, 101, 34, 90, 16, 142, 101, 186, 10, 160, 101, 110, 74, 213, 129, 67, 66, 163, 2, 17, 0, 0, 0, 4, 33, 91, 191, 137, 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: