Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28d936c4dcd2fa8e2b6936205ba1c592e30addebb354e7341e5eb5d1e3e16943

Tx prefix hash: 745be8da59af093de552c696e8b84dd3e8a97fddcf4d9db6d0d5432279c07ca3
Tx public key: 13d41b4068a61ac891d0a4c20bb7ff86a4de618b9dc3731b94feeb1d9b641bd8
Timestamp: 1766466634 Timestamp [UTC]: 2025-12-23 05:10:34 Age [y:d:h:m:s]: 00:331:06:03:48
Block: 1439647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242196 RingCT/type: yes/0
Extra: 0113d41b4068a61ac891d0a4c20bb7ff86a4de618b9dc3731b94feeb1d9b641bd80211000000027b1e51ac000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd3d7255b14b92894716dc1a00d1816947f6496fd483c0da7bf1250acd50c05e 0.000600000000 1928494 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": 1439657, "vin": [ { "gen": { "height": 1439647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd3d7255b14b92894716dc1a00d1816947f6496fd483c0da7bf1250acd50c05e" } } ], "extra": [ 1, 19, 212, 27, 64, 104, 166, 26, 200, 145, 208, 164, 194, 11, 183, 255, 134, 164, 222, 97, 139, 157, 195, 115, 27, 148, 254, 235, 29, 155, 100, 27, 216, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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: