Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79df4cd76993621cfc9b40148f4be07dfa30aeb07e8d6ba795b5794d3b4c7bd8

Tx prefix hash: d08b9262df0cd43fae2337fa3c61a48e5825b101efa25fc3bce2fd0d86c248cf
Tx public key: b13958624303f1cab7684bcd26cc1c8e8fe2e56dd218e955357e7620bdb4801d
Timestamp: 1748290126 Timestamp [UTC]: 2025-05-26 20:08:46 Age [y:d:h:m:s]: 01:176:16:47:42
Block: 1291560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390337 RingCT/type: yes/0
Extra: 01b13958624303f1cab7684bcd26cc1c8e8fe2e56dd218e955357e7620bdb4801d021100000004523560da000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8e0026674490a4fa17e77be7a1b95a76fe81f5c5bbe58abcb668879ebf3a37af 0.000600000000 1779031 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": 1291570, "vin": [ { "gen": { "height": 1291560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e0026674490a4fa17e77be7a1b95a76fe81f5c5bbe58abcb668879ebf3a37af" } } ], "extra": [ 1, 177, 57, 88, 98, 67, 3, 241, 202, 183, 104, 75, 205, 38, 204, 28, 142, 143, 226, 229, 109, 210, 24, 233, 85, 53, 126, 118, 32, 189, 180, 128, 29, 2, 17, 0, 0, 0, 4, 82, 53, 96, 218, 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: