Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28b475b96e6c3d0a5d401ed858b41c7dce4c5a1b6e2a1a4ce2f99de19a3cdc11

Tx prefix hash: bc71e8386f32c05a3ce85c4d2a5397b594af6cfa11b30da4c4ee49a4e51cb47d
Tx public key: 41ed78a57d5881ed9982c0d1e1e00ee1a1c9cd2beff3334ea8fce79cb3eaf87c
Timestamp: 1789608355 Timestamp [UTC]: 2026-09-17 01:25:55 Age [y:d:h:m:s]: 00:061:00:30:28
Block: 1637116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 42947 RingCT/type: yes/0
Extra: 0141ed78a57d5881ed9982c0d1e1e00ee1a1c9cd2beff3334ea8fce79cb3eaf87c

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bdfcf81d449399f69a398bbf4113b080ad21d2e0f9b517189821987aae500fe1 0.000600000000 2127146 of 15 <42>

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": 1637126, "vin": [ { "gen": { "height": 1637116 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "bdfcf81d449399f69a398bbf4113b080ad21d2e0f9b517189821987aae500fe1", "view_tag": "42" } } } ], "extra": [ 1, 65, 237, 120, 165, 125, 88, 129, 237, 153, 130, 192, 209, 225, 224, 14, 225, 161, 201, 205, 43, 239, 243, 51, 78, 168, 252, 231, 156, 179, 234, 248, 124 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: