Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 121baeef7cbda59bf7bffb03db064f4740da82b85169cffbf6927772644f1f97

Tx prefix hash: 2141ca0c338930f77f849016abcdb60b6bc87b6a6dda35838f928b9ee75d5d67
Tx public key: cbfa5975ddfb535db9a641b64cdeaa5cc60c77907fb7c1ad01dd35fa2082821d
Timestamp: 1771339436 Timestamp [UTC]: 2026-02-17 14:43:56 Age [y:d:h:m:s]: 00:271:18:03:26
Block: 1479828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199706 RingCT/type: yes/0
Extra: 01cbfa5975ddfb535db9a641b64cdeaa5cc60c77907fb7c1ad01dd35fa2082821d021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b1a766ecb8b0fef8cef473fea3f687743fdb0fb4d687f8527fee471bcb78e46 0.000600000000 1969184 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": 1479838, "vin": [ { "gen": { "height": 1479828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b1a766ecb8b0fef8cef473fea3f687743fdb0fb4d687f8527fee471bcb78e46" } } ], "extra": [ 1, 203, 250, 89, 117, 221, 251, 83, 93, 185, 166, 65, 182, 76, 222, 170, 92, 198, 12, 119, 144, 127, 183, 193, 173, 1, 221, 53, 250, 32, 130, 130, 29, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: