Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f7912c3eea6dad63449384e70e9a112808f604f59f2c2ebc28a50eb6f941c23

Tx prefix hash: 9833b523bd2a934fec1702dc394c03ded2cdbcd0f8b181894f1c5a6ea0a89955
Tx public key: 6e76a048c4e078d7ef439230e0c952cc72e51544ae74d44a79a2a03610164485
Timestamp: 1770144537 Timestamp [UTC]: 2026-02-03 18:48:57 Age [y:d:h:m:s]: 00:290:00:00:37
Block: 1469976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 212896 RingCT/type: yes/0
Extra: 016e76a048c4e078d7ef439230e0c952cc72e51544ae74d44a79a2a036101644850208aa7ee94a6d68f4aa

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fa7e416b7034fd1c29d9ef59a1e29937345742a780fe94037ef249a39b5b452c 0.000600000000 1959242 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": 1469986, "vin": [ { "gen": { "height": 1469976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa7e416b7034fd1c29d9ef59a1e29937345742a780fe94037ef249a39b5b452c" } } ], "extra": [ 1, 110, 118, 160, 72, 196, 224, 120, 215, 239, 67, 146, 48, 224, 201, 82, 204, 114, 229, 21, 68, 174, 116, 212, 74, 121, 162, 160, 54, 16, 22, 68, 133, 2, 8, 170, 126, 233, 74, 109, 104, 244, 170 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: