Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a23941901d103a7e5b1b44e0e1e290e0351692224545ea4c2bccc8e6f9236899

Tx prefix hash: 14dbecabbacde1ae79de0852b6e21d40d572d0b023a44df4e5b19fb201e7b321
Tx public key: f2eeea252610df4018a64ac39ced8b6cb22664bfe5d2199b4cc51b9bce10e98a
Timestamp: 1737386797 Timestamp [UTC]: 2025-01-20 15:26:37 Age [y:d:h:m:s]: 01:302:07:03:31
Block: 1201504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479931 RingCT/type: yes/0
Extra: 01f2eeea252610df4018a64ac39ced8b6cb22664bfe5d2199b4cc51b9bce10e98a021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf3c0120e04b97e9709fa38fb123930df02284cbaa53d6218ea31aa27d286a0e 0.000600000000 1688157 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": 1201514, "vin": [ { "gen": { "height": 1201504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf3c0120e04b97e9709fa38fb123930df02284cbaa53d6218ea31aa27d286a0e" } } ], "extra": [ 1, 242, 238, 234, 37, 38, 16, 223, 64, 24, 166, 74, 195, 156, 237, 139, 108, 178, 38, 100, 191, 229, 210, 25, 155, 76, 197, 27, 155, 206, 16, 233, 138, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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: