Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed2225c2b9787bb601b6e43efffefeb78d8361af38dafd2628f532f113cec416

Tx prefix hash: 307ee1b347121d453d7f4b2fd5cfecefeb3a64b25f7599681e15dee54ccfab47
Tx public key: f3ec03dd9edce51cac735228052cffc41a8cfd579f6185c687e5d4f63101fbfb
Timestamp: 1773986043 Timestamp [UTC]: 2026-03-20 05:54:03 Age [y:d:h:m:s]: 00:244:21:55:05
Block: 1501713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180664 RingCT/type: yes/0
Extra: 01f3ec03dd9edce51cac735228052cffc41a8cfd579f6185c687e5d4f63101fbfb021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5d6ca0d119968d6552c9e5c74ac664f47d512267f4f7b55bff96e77282ef19e6 0.000600000000 1991399 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": 1501723, "vin": [ { "gen": { "height": 1501713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d6ca0d119968d6552c9e5c74ac664f47d512267f4f7b55bff96e77282ef19e6" } } ], "extra": [ 1, 243, 236, 3, 221, 158, 220, 229, 28, 172, 115, 82, 40, 5, 44, 255, 196, 26, 140, 253, 87, 159, 97, 133, 198, 135, 229, 212, 246, 49, 1, 251, 251, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: