Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a481e93cb0a3c6eaf40eaabd43fd7d5362ee8de38c96502ad2c988ca029f89

Tx prefix hash: 8f3452c09c4e50d2a8bceb4da6887f5328376dd21369043e886c049179677317
Tx public key: ec9a322068d74dd6bd131197fdee461a25ce042e5fdbada2753529697651929f
Timestamp: 1743993384 Timestamp [UTC]: 2025-04-07 02:36:24 Age [y:d:h:m:s]: 01:041:17:43:28
Block: 1255956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280970 RingCT/type: yes/0
Extra: 01ec9a322068d74dd6bd131197fdee461a25ce042e5fdbada2753529697651929f021100000002dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5feb73f092ff68f72f0ae9a7b0f36f8a97e0a1da9a933d725beeeb8a60087d14 0.000600000000 1743063 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": 1255966, "vin": [ { "gen": { "height": 1255956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5feb73f092ff68f72f0ae9a7b0f36f8a97e0a1da9a933d725beeeb8a60087d14" } } ], "extra": [ 1, 236, 154, 50, 32, 104, 215, 77, 214, 189, 19, 17, 151, 253, 238, 70, 26, 37, 206, 4, 46, 95, 219, 173, 162, 117, 53, 41, 105, 118, 81, 146, 159, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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: