Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ece5c572ea76a6151095c0e5c2fff4f1d037e4f08938a1433896bdfd82ae91ba

Tx prefix hash: 0dc54361201cb752ff150cbaa0632a6b64c52b77d66992d52a8be6ba168b01eb
Tx public key: b97e0386ddcf0e5a37c01ba24b1d40e566ac58813079c8ab8cb0b5192db750c3
Timestamp: 1773706425 Timestamp [UTC]: 2026-03-17 00:13:45 Age [y:d:h:m:s]: 00:249:17:49:45
Block: 1499427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184067 RingCT/type: yes/0
Extra: 01b97e0386ddcf0e5a37c01ba24b1d40e566ac58813079c8ab8cb0b5192db750c3021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1b69a731e0efb0c5862f1d242127dff1b1280fbf4939c7ee276816b1cfcb9321 0.000600000000 1989085 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": 1499437, "vin": [ { "gen": { "height": 1499427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b69a731e0efb0c5862f1d242127dff1b1280fbf4939c7ee276816b1cfcb9321" } } ], "extra": [ 1, 185, 126, 3, 134, 221, 207, 14, 90, 55, 192, 27, 162, 75, 29, 64, 229, 102, 172, 88, 129, 48, 121, 200, 171, 140, 176, 181, 25, 45, 183, 80, 195, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: