Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b432fc16564adfa0703c5d7425bc50dddf3c06bef4f183c4f89452984b638bc4

Tx prefix hash: 3142917e680f7b5c97aa7b45a5a61b05980d927664bf5737b4ccb534bfcde3a7
Tx public key: 747df173b1cbb443085afaf8974fef12ccc7d162caddfb0c18cb4ba6fb5d6571
Timestamp: 1756974067 Timestamp [UTC]: 2025-09-04 08:21:07 Age [y:d:h:m:s]: 00:247:18:39:05
Block: 1361056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169739 RingCT/type: yes/0
Extra: 01747df173b1cbb443085afaf8974fef12ccc7d162caddfb0c18cb4ba6fb5d6571021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f4bb9b61d0318be903bcf1cb976ccb59d4d0ad611ff4f3d296b29f9c2186bad0 0.000600000000 1849069 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": 1361066, "vin": [ { "gen": { "height": 1361056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4bb9b61d0318be903bcf1cb976ccb59d4d0ad611ff4f3d296b29f9c2186bad0" } } ], "extra": [ 1, 116, 125, 241, 115, 177, 203, 180, 67, 8, 90, 250, 248, 151, 79, 239, 18, 204, 199, 209, 98, 202, 221, 251, 12, 24, 203, 75, 166, 251, 93, 101, 113, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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: