Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ec73505916f5cf66fb159bdd53949e375a25ce8c58ec1b82e6efcd6508b2b1b

Tx prefix hash: bcbd82b48ce1e3aa24a7360e94cfa31a3236d240370c4a841368f053338b3a2a
Tx public key: ae86c98f7d307f6142eb5d83e23a1062390ece1ea7e56c2ec4e25ebfbb0cdcf7
Timestamp: 1582196932 Timestamp [UTC]: 2020-02-20 11:08:52 Age [y:d:h:m:s]: 06:273:07:11:41
Block: 68816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1612493 RingCT/type: yes/0
Extra: 01ae86c98f7d307f6142eb5d83e23a1062390ece1ea7e56c2ec4e25ebfbb0cdcf7021100000001724f989b000000000000000000

1 output(s) for total of 0.363065373043 xmr

stealth address amount amount idx tag
00: 5939bc7a811d75291227b4b9bf090d86e32de63420c0a183f21517c2f4f29af9 0.363065373043 126857 of 0 -

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": 68826, "vin": [ { "gen": { "height": 68816 } } ], "vout": [ { "amount": 363065373043, "target": { "key": "5939bc7a811d75291227b4b9bf090d86e32de63420c0a183f21517c2f4f29af9" } } ], "extra": [ 1, 174, 134, 201, 143, 125, 48, 127, 97, 66, 235, 93, 131, 226, 58, 16, 98, 57, 14, 206, 30, 167, 229, 108, 46, 196, 226, 94, 191, 187, 12, 220, 247, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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: