Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ee35d54a547d61bc03e13525380a11dd516f9c4bf63bd75852d116c30bd4e2d

Tx prefix hash: 0c902c383b3b88367bed9ceb57f644b6f4599c1206a921cbc1f10af7dfb48d98
Tx public key: 4df1365244a3c11ac6e89d0c668224c6b4bd8b2f294216f6cffe791e00afba03
Timestamp: 1745785778 Timestamp [UTC]: 2025-04-27 20:29:38 Age [y:d:h:m:s]: 01:205:21:16:03
Block: 1270819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411231 RingCT/type: yes/0
Extra: 014df1365244a3c11ac6e89d0c668224c6b4bd8b2f294216f6cffe791e00afba030211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6cf0e5b96841360c2b1523dd19962ec05eab4a6c0c09f3b928bdccf48ce90d36 0.000600000000 1758064 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": 1270829, "vin": [ { "gen": { "height": 1270819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cf0e5b96841360c2b1523dd19962ec05eab4a6c0c09f3b928bdccf48ce90d36" } } ], "extra": [ 1, 77, 241, 54, 82, 68, 163, 193, 26, 198, 232, 157, 12, 102, 130, 36, 198, 180, 189, 139, 47, 41, 66, 22, 246, 207, 254, 121, 30, 0, 175, 186, 3, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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: