Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28a5fecda414d112c3b106723d7ed920206d7ac385ca7da437257e922489b07

Tx prefix hash: 08d3555ecd5269fdf5e2ad24f65868fc546f9a6e4f6652ce7ac3322438d62454
Tx public key: 673e6f0138f4004bd1429609a3e7a397716d0b20e929a7c3318217ace232f674
Timestamp: 1750539842 Timestamp [UTC]: 2025-06-21 21:04:02 Age [y:d:h:m:s]: 01:062:21:58:27
Block: 1310005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309411 RingCT/type: yes/0
Extra: 01673e6f0138f4004bd1429609a3e7a397716d0b20e929a7c3318217ace232f67402110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 912dce153a3987f49d90be61960a86016af14dce4c5f290f8ba4c410d130dafe 0.000600000000 1797622 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": 1310015, "vin": [ { "gen": { "height": 1310005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "912dce153a3987f49d90be61960a86016af14dce4c5f290f8ba4c410d130dafe" } } ], "extra": [ 1, 103, 62, 111, 1, 56, 244, 0, 75, 209, 66, 150, 9, 163, 231, 163, 151, 113, 109, 11, 32, 233, 41, 167, 195, 49, 130, 23, 172, 226, 50, 246, 116, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: