Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b592c2e5c242c784ca477885d31c96f59ffe1fc1a6732e53889ca10006680b02

Tx prefix hash: 3f0fa779458c23f4ee549e0b17fbb7c3b82fa602fd377af00f7785b1ebd73d3d
Tx public key: c640e282998d72b56e1db9e2e0362191bdf1deefb1e5058dd8bf88aa0e1a13b4
Timestamp: 1772417406 Timestamp [UTC]: 2026-03-02 02:10:06 Age [y:d:h:m:s]: 00:264:13:34:52
Block: 1488756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194738 RingCT/type: yes/0
Extra: 01c640e282998d72b56e1db9e2e0362191bdf1deefb1e5058dd8bf88aa0e1a13b4021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c67ec731221eb2f6b7752a73d039038a70f209ceb3e86ae2950c243d18339865 0.000600000000 1978236 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": 1488766, "vin": [ { "gen": { "height": 1488756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c67ec731221eb2f6b7752a73d039038a70f209ceb3e86ae2950c243d18339865" } } ], "extra": [ 1, 198, 64, 226, 130, 153, 141, 114, 181, 110, 29, 185, 226, 224, 54, 33, 145, 189, 241, 222, 239, 177, 229, 5, 141, 216, 191, 136, 170, 14, 26, 19, 180, 2, 17, 0, 0, 0, 2, 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: