Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59120122255a6d496a1f7d6e5f22b5b1dc452c71c78cb75a1e48b07ee2baa17e

Tx prefix hash: 406f302288d3318caa9edf4ad2fd7957edbd9fa412b59644237e4c5d0e1a80a4
Tx public key: 33793d271e4879e05ee755e1fa0e74d123b0448dc7f0b83496c8482842804b73
Timestamp: 1757325608 Timestamp [UTC]: 2025-09-08 10:00:08 Age [y:d:h:m:s]: 00:350:09:24:40
Block: 1363991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256165 RingCT/type: yes/0
Extra: 0133793d271e4879e05ee755e1fa0e74d123b0448dc7f0b83496c8482842804b73021100000008b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c091147b07f591283331af94ef59c22c689d710399690a1db52c3afa96375602 0.000600000000 1852030 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": 1364001, "vin": [ { "gen": { "height": 1363991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c091147b07f591283331af94ef59c22c689d710399690a1db52c3afa96375602" } } ], "extra": [ 1, 51, 121, 61, 39, 30, 72, 121, 224, 94, 231, 85, 225, 250, 14, 116, 209, 35, 176, 68, 141, 199, 240, 184, 52, 150, 200, 72, 40, 66, 128, 75, 115, 2, 17, 0, 0, 0, 8, 178, 247, 132, 196, 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: