Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f62bbad7f6d378fc4749f2b3c5e1c09662f6287c2aba769ce419db40a61bff81

Tx prefix hash: 50df58324350467d784b20f731c51e3979cec37ae9b86eff052f3df1898eb2cb
Tx public key: 5eda1dca6bfcd472f685beea4ce2f3ad4726e938edeb7a1676896898287a1519
Timestamp: 1743655153 Timestamp [UTC]: 2025-04-03 04:39:13 Age [y:d:h:m:s]: 01:230:21:17:09
Block: 1253170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429144 RingCT/type: yes/0
Extra: 015eda1dca6bfcd472f685beea4ce2f3ad4726e938edeb7a1676896898287a1519021100000005a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cff328b174e4a79045c1b932e60e1b355d71ea9ae0409132a7072643b7306df1 0.000600000000 1740251 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": 1253180, "vin": [ { "gen": { "height": 1253170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cff328b174e4a79045c1b932e60e1b355d71ea9ae0409132a7072643b7306df1" } } ], "extra": [ 1, 94, 218, 29, 202, 107, 252, 212, 114, 246, 133, 190, 234, 76, 226, 243, 173, 71, 38, 233, 56, 237, 235, 122, 22, 118, 137, 104, 152, 40, 122, 21, 25, 2, 17, 0, 0, 0, 5, 162, 237, 1, 107, 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: