Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c58c36affc97d67a8bd66be45d5c2e1c4b6f34b8b038dee52f11058d40eec5

Tx prefix hash: 2a82116066eb6fd8b586b82f8e847dfff95a8676b8527c4e34f367e71ccf54b3
Tx public key: 146600739bc07da79f7dee25efce8b926b2e8c2e8f769154a837a337270fe51e
Timestamp: 1761153775 Timestamp [UTC]: 2025-10-22 17:22:55 Age [y:d:h:m:s]: 01:023:20:17:00
Block: 1395630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283303 RingCT/type: yes/0
Extra: 01146600739bc07da79f7dee25efce8b926b2e8c2e8f769154a837a337270fe51e02110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2947f8ee7f81d0c64f88e15bf0cffd840a816223adf38d7f4cecf208474abe0e 0.000600000000 1883913 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": 1395640, "vin": [ { "gen": { "height": 1395630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2947f8ee7f81d0c64f88e15bf0cffd840a816223adf38d7f4cecf208474abe0e" } } ], "extra": [ 1, 20, 102, 0, 115, 155, 192, 125, 167, 159, 125, 238, 37, 239, 206, 139, 146, 107, 46, 140, 46, 143, 118, 145, 84, 168, 55, 163, 55, 39, 15, 229, 30, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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: