Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71db369f99b9fa5556bc66bcd32fc8a57263740276bb0e433b46c337fbae09fa

Tx prefix hash: 5f230b5a181e0f6e4f78f267463fd389afe6c6ac72e23b3f864ab538fdd12885
Tx public key: 3549265bf23ae7410c8fdaaa1f745241076e46765154a858cd094a410e55b7e4
Timestamp: 1720651693 Timestamp [UTC]: 2024-07-10 22:48:13 Age [y:d:h:m:s]: 01:218:05:56:50
Block: 1062966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414418 RingCT/type: yes/0
Extra: 013549265bf23ae7410c8fdaaa1f745241076e46765154a858cd094a410e55b7e4021100000007e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9bb3aea08541011e2d767c8a4250f67d44f390c1d41d47810d80365813990cf2 0.000600000000 1533477 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": 1062976, "vin": [ { "gen": { "height": 1062966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bb3aea08541011e2d767c8a4250f67d44f390c1d41d47810d80365813990cf2" } } ], "extra": [ 1, 53, 73, 38, 91, 242, 58, 231, 65, 12, 143, 218, 170, 31, 116, 82, 65, 7, 110, 70, 118, 81, 84, 168, 88, 205, 9, 74, 65, 14, 85, 183, 228, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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) | dinastycoin version: tesla-369