Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc4966fd9a0b1e05d529ff86f06f7666495341fcb4800e71e8280c01cafd09f4

Tx prefix hash: b6faf89a85e79966b36ff5c23849228b0329bdbad98189d2f99c534be9910099
Tx public key: dd98444e789592bb003ad187040b5151b4b6ca3f3fa6c3ed04c0f247971a7514
Timestamp: 1757840413 Timestamp [UTC]: 2025-09-14 09:00:13 Age [y:d:h:m:s]: 00:344:18:34:41
Block: 1368158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252249 RingCT/type: yes/0
Extra: 01dd98444e789592bb003ad187040b5151b4b6ca3f3fa6c3ed04c0f247971a7514021100000006ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a35a6032bc55c152af7c8ae4d0160a81cb8e6004e013a68d795066997d654e5f 0.000600000000 1856201 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": 1368168, "vin": [ { "gen": { "height": 1368158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a35a6032bc55c152af7c8ae4d0160a81cb8e6004e013a68d795066997d654e5f" } } ], "extra": [ 1, 221, 152, 68, 78, 120, 149, 146, 187, 0, 58, 209, 135, 4, 11, 81, 81, 180, 182, 202, 63, 63, 166, 195, 237, 4, 192, 242, 71, 151, 26, 117, 20, 2, 17, 0, 0, 0, 6, 173, 121, 72, 208, 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: