Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ade3cd1afd5ba3201834f38eed44f13fe68a72dc1baf64a047f77dfc409bd652

Tx prefix hash: b0259e7044c1b086dad4e23b96c3cb79d0ec2cf23a5b760f9a73bc04e084b110
Tx public key: a031340a12f1a6b2a891fb4c2a460971ca19f5002954f8c41a5c74545f9696bf
Timestamp: 1771770674 Timestamp [UTC]: 2026-02-22 14:31:14 Age [y:d:h:m:s]: 00:269:19:59:06
Block: 1483406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198414 RingCT/type: yes/0
Extra: 01a031340a12f1a6b2a891fb4c2a460971ca19f5002954f8c41a5c74545f9696bf021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3505dd6c35b1dc7d9e64c199599010c362ff6fd6205a3679d2846b2f3c9420f6 0.000600000000 1972814 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": 1483416, "vin": [ { "gen": { "height": 1483406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3505dd6c35b1dc7d9e64c199599010c362ff6fd6205a3679d2846b2f3c9420f6" } } ], "extra": [ 1, 160, 49, 52, 10, 18, 241, 166, 178, 168, 145, 251, 76, 42, 70, 9, 113, 202, 25, 245, 0, 41, 84, 248, 196, 26, 92, 116, 84, 95, 150, 150, 191, 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: