Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9407ff0a7ce526b54abb2cbd03e3a2aa32d2d9a3eb000f74eb16dc3ac13fcb2

Tx prefix hash: b98fdaaa8b8f68b7f2e6f66c2edf54da275b59adf175966fe2fc7dcdc061aba1
Tx public key: 204878273f53169cabf28a7920d199eeb57d003df17303a81945bb64827b5ee8
Timestamp: 1746364547 Timestamp [UTC]: 2025-05-04 13:15:47 Age [y:d:h:m:s]: 01:005:15:17:39
Block: 1275602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255240 RingCT/type: yes/0
Extra: 01204878273f53169cabf28a7920d199eeb57d003df17303a81945bb64827b5ee80211000000051f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c04a3b52baf29b780fc880a9e721821e7e8f6f8772b3dfa3f92ce894b16e2e78 0.000600000000 1762917 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": 1275612, "vin": [ { "gen": { "height": 1275602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04a3b52baf29b780fc880a9e721821e7e8f6f8772b3dfa3f92ce894b16e2e78" } } ], "extra": [ 1, 32, 72, 120, 39, 63, 83, 22, 156, 171, 242, 138, 121, 32, 209, 153, 238, 181, 125, 0, 61, 241, 115, 3, 168, 25, 69, 187, 100, 130, 123, 94, 232, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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: