Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef7b7954cb70d2f7377b86dc76c42c61f8aa6080154bee7ebb9ff8a945229837

Tx prefix hash: a3ea58d6a20f8053d1120b8d437f2c2271ded3f50a6b5642e68a122f2da75298
Tx public key: ae7a366f6f3afb51be03be99e9312ec7c409f0d19978ecc06d9ca08c2a729baf
Timestamp: 1746342608 Timestamp [UTC]: 2025-05-04 07:10:08 Age [y:d:h:m:s]: 01:009:01:13:38
Block: 1275427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257297 RingCT/type: yes/0
Extra: 01ae7a366f6f3afb51be03be99e9312ec7c409f0d19978ecc06d9ca08c2a729baf0211000000121f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a969faf0d13d29d8c57e5422bdc0f2ef9d3aee2f0140f7a926b47fd56fc6954d 0.000600000000 1762738 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": 1275437, "vin": [ { "gen": { "height": 1275427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a969faf0d13d29d8c57e5422bdc0f2ef9d3aee2f0140f7a926b47fd56fc6954d" } } ], "extra": [ 1, 174, 122, 54, 111, 111, 58, 251, 81, 190, 3, 190, 153, 233, 49, 46, 199, 196, 9, 240, 209, 153, 120, 236, 192, 109, 156, 160, 140, 42, 114, 155, 175, 2, 17, 0, 0, 0, 18, 31, 144, 81, 122, 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: