Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1ba52d1b8f6ce4a59f3d69204f90a29cb4156685f8a55f7bfa4755e3bbe78b7

Tx prefix hash: a55627f76aa14d3e2ba1b68e4ef70ce1b1325d277b37a125924715c6599c63b8
Tx public key: cb1de134558bb5d9b68fa4a0946d0f4cbbef84a85df348a1ee004e1d23add4da
Timestamp: 1744859033 Timestamp [UTC]: 2025-04-17 03:03:53 Age [y:d:h:m:s]: 01:026:02:20:15
Block: 1263137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269482 RingCT/type: yes/0
Extra: 01cb1de134558bb5d9b68fa4a0946d0f4cbbef84a85df348a1ee004e1d23add4da0211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b44eab5ecd5983dbd640012a12930f0c633e7d0a8ed0ba0dcb40dcb7234e2a59 0.000600000000 1750320 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": 1263147, "vin": [ { "gen": { "height": 1263137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b44eab5ecd5983dbd640012a12930f0c633e7d0a8ed0ba0dcb40dcb7234e2a59" } } ], "extra": [ 1, 203, 29, 225, 52, 85, 139, 181, 217, 182, 143, 164, 160, 148, 109, 15, 76, 187, 239, 132, 168, 93, 243, 72, 161, 238, 0, 78, 29, 35, 173, 212, 218, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: