Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6098efbee72efdfd6de258ffc4a70fe3979e763c5bad4c9ce5a179dca3ffdc73

Tx prefix hash: 733afb55d023d46cfafee800890307fcbdda17a3df411c58e06cad021f7353ad
Tx public key: 774568f13af7f848bcb473dece04f099779ffe2600662f1cc826c3a7f226987a
Timestamp: 1737340627 Timestamp [UTC]: 2025-01-20 02:37:07 Age [y:d:h:m:s]: 01:183:19:53:19
Block: 1201121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381993 RingCT/type: yes/0
Extra: 01774568f13af7f848bcb473dece04f099779ffe2600662f1cc826c3a7f226987a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b8a8feb84c2896f16b686709f4c697ccd8c6f324051fe32c63c34021618d3572 0.000600000000 1687770 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": 1201131, "vin": [ { "gen": { "height": 1201121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a8feb84c2896f16b686709f4c697ccd8c6f324051fe32c63c34021618d3572" } } ], "extra": [ 1, 119, 69, 104, 241, 58, 247, 248, 72, 188, 180, 115, 222, 206, 4, 240, 153, 119, 159, 254, 38, 0, 102, 47, 28, 200, 38, 195, 167, 242, 38, 152, 122, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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: