Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6498c6f6e5883eb0f63f0811b618fb13a15beed034f31b8eb8cc35d9ba6ed91f

Tx prefix hash: 8bbd132e40ad6242abac8cd317137783df126cc4db3c496d8a14de1eb23ab64d
Tx public key: 21f0bd091c2415513b4445ec1107e39d3923dfc0b005bddd522c6bd8c3481fa5
Timestamp: 1741743856 Timestamp [UTC]: 2025-03-12 01:44:16 Age [y:d:h:m:s]: 00:341:13:08:39
Block: 1237361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241754 RingCT/type: yes/0
Extra: 0121f0bd091c2415513b4445ec1107e39d3923dfc0b005bddd522c6bd8c3481fa50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cdda28c58c26abd6479c17c2af5014f903313d720d12e6ea94c06a78fef7099b 0.000600000000 1724316 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": 1237371, "vin": [ { "gen": { "height": 1237361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdda28c58c26abd6479c17c2af5014f903313d720d12e6ea94c06a78fef7099b" } } ], "extra": [ 1, 33, 240, 189, 9, 28, 36, 21, 81, 59, 68, 69, 236, 17, 7, 227, 157, 57, 35, 223, 192, 176, 5, 189, 221, 82, 44, 107, 216, 195, 72, 31, 165, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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