Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f002a515b8f2d37ff01009f9a9c296f1940efb9deb461fcc658a571cb5c49eb

Tx prefix hash: 75fc5ae5d1d3647d56460c5d7a0a2774a22e01c4cc44f2bc155fbefc5b35f103
Tx public key: 2c25146592d9650d5bf712b9017fc3095d33b8e981163e354bb05831e5294fca
Timestamp: 1766721939 Timestamp [UTC]: 2025-12-26 04:05:39 Age [y:d:h:m:s]: 00:053:18:07:41
Block: 1441763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38281 RingCT/type: yes/0
Extra: 012c25146592d9650d5bf712b9017fc3095d33b8e981163e354bb05831e5294fca02110000000770609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cdf2f4ef4e4e9bf9b435b8e27eb4854dc200ca9fc2f5bb1b453a0965a731ed7b 0.000600000000 1930658 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": 1441773, "vin": [ { "gen": { "height": 1441763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdf2f4ef4e4e9bf9b435b8e27eb4854dc200ca9fc2f5bb1b453a0965a731ed7b" } } ], "extra": [ 1, 44, 37, 20, 101, 146, 217, 101, 13, 91, 247, 18, 185, 1, 127, 195, 9, 93, 51, 184, 233, 129, 22, 62, 53, 75, 176, 88, 49, 229, 41, 79, 202, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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) | dinastycoin version: tesla-369