Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84ac78900d6ac60998c83f3aeeba00501ec21138c6fa6ced02151e85bbec3f13

Tx prefix hash: b41c0e75315cf2d90a6de161e38e70bea5401fc56a0cce670774bb97f7af3a0f
Tx public key: afa1a934c58acb98e6b10447ea48ec495a53843a75f4250b489dbec950f4f4ad
Timestamp: 1719712399 Timestamp [UTC]: 2024-06-30 01:53:19 Age [y:d:h:m:s]: 02:142:19:45:29
Block: 1055162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 627016 RingCT/type: yes/0
Extra: 01afa1a934c58acb98e6b10447ea48ec495a53843a75f4250b489dbec950f4f4ad02110000000359dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7e2770ccd0edeeb1e2a4aac81d017fc1e482d3b75c1911c819f9dae6f13ddbc8 0.000600000000 1525555 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": 1055172, "vin": [ { "gen": { "height": 1055162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e2770ccd0edeeb1e2a4aac81d017fc1e482d3b75c1911c819f9dae6f13ddbc8" } } ], "extra": [ 1, 175, 161, 169, 52, 197, 138, 203, 152, 230, 177, 4, 71, 234, 72, 236, 73, 90, 83, 132, 58, 117, 244, 37, 11, 72, 157, 190, 201, 80, 244, 244, 173, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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: